Hi Felipe,
On Fri, Aug 29, 2014 at 12:46 AM, Felipe Balbi wrote:
> hi,
>
> On Thu, Aug 28, 2014 at 01:31:58PM +0530, Vivek Gautam wrote:
>> @@ -457,11 +458,19 @@ static int exynos5_usbdrd_phy_power_on(struct phy *phy)
>> clk_prepare_enable(phy_drd->ref_clk);
>>
>> /* Enable VBUS supp
On Thu, Aug 28, 2014 at 8:36 PM, Daniele Forsi wrote:
> 2014-08-28 10:02 GMT+02:00 Vivek Gautam:
>
>> This USB 3.0 PHY controller is also present on Exynos7
>> platform, so adding the dependency on ARCH_EXYNOS7 for this driver.
>
>> +++ b/drivers/phy/Kconfig
>> @@ -186,7 +186,7 @@ config PHY_EXYNO
On Sat, 30 Aug 2014, Octavian Purdila wrote:
> This patch implements the USB part of the Diolan USB-I2C/SPI/GPIO
> Master Adapter DLN-2. Details about the device can be found here:
>
> https://www.diolan.com/i2c/i2c_interface.html.
>
> Information about the USB protocol can be found in the Progr
Hello
The promised dmesg output. Still some "xhci_drop_endpoint called with..."
Thanks!
Sep 1 10:52:00 neopili kernel: [ 193.123108] usb 2-2: new SuperSpeed
USB device number 2 using xhci_hcd
Sep 1 10:52:00 neopili kernel: [ 193.142204] usb 2-2: New USB device
found, idVendor=0525, idProduct
On Mon, Sep 1, 2014 at 11:37 AM, Lee Jones wrote:
> On Sat, 30 Aug 2014, Octavian Purdila wrote:
>
>> This patch implements the USB part of the Diolan USB-I2C/SPI/GPIO
>> Master Adapter DLN-2. Details about the device can be found here:
>>
>> https://www.diolan.com/i2c/i2c_interface.html.
>>
>> In
After some time of use (one hour or so) my system started to behave
"weird". I did check dmesg and I was receiving the following line
again and again:
usb-storage: Error in queuecommand_lck: us->sfb= 8805bd61ccc0
I did disconnect the usb device and the whole computer crashed :S
On Mon, Se
Signed-off-by: Frans Klaver
---
drivers/usb/serial/xsens_mt.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/serial/xsens_mt.c b/drivers/usb/serial/xsens_mt.c
index 4841fb5..d500ccd 100644
--- a/drivers/usb/serial/xsens_mt.c
+++ b/drivers/usb/serial/xsens_mt.c
@@ -82,4 +82,6 @@
Probe is testing if the current interface provides two bulk endpoints.
While this achieves the goal of only binding to the correct interface,
we already know we can find the device on interface number 1. Stop
checking the endpoints and just return successfully when interface
number 1 is probed.
Si
On Mon, 01 Sep 2014, Octavian Purdila wrote:
> On Mon, Sep 1, 2014 at 11:37 AM, Lee Jones wrote:
> > On Sat, 30 Aug 2014, Octavian Purdila wrote:
> >
> >> This patch implements the USB part of the Diolan USB-I2C/SPI/GPIO
> >> Master Adapter DLN-2. Details about the device can be found here:
> >>
On Thu, Aug 28, 2014 at 03:08:16PM +0200, Bjørn Mork wrote:
> This VID:PID is used for some Direct IP devices behaving
> identical to the already supported 0F3D:68AA devices.
>
> Cc:
> Reported-by: Lars Melin
> Signed-off-by: Bjørn Mork
> ---
> This should be applied on top of my 'USB: sierra:
Hi,
On Friday, August 29, 2014 11:33:04 AM Greg Kroah-Hartman wrote:
> On Fri, Aug 29, 2014 at 11:02:52AM +0200, Bartlomiej Zolnierkiewicz wrote:
> > On Thursday, August 28, 2014 12:29:52 PM Greg Kroah-Hartman wrote:
> > > On Thu, Aug 28, 2014 at 08:11:04PM +0200, Bartlomiej Zolnierkiewicz wrote:
On Mon, Sep 1, 2014 at 12:51 PM, Lee Jones wrote:
> On Mon, 01 Sep 2014, Octavian Purdila wrote:
>
>> On Mon, Sep 1, 2014 at 11:37 AM, Lee Jones wrote:
>> > On Sat, 30 Aug 2014, Octavian Purdila wrote:
>> >
>> >> This patch implements the USB part of the Diolan USB-I2C/SPI/GPIO
>> >> Master Adapt
On 09/01/2014 12:36 PM, Ricardo Ribalda Delgado wrote:
> After some time of use (one hour or so) my system started to behave
> "weird". I did check dmesg and I was receiving the following line
> again and again:
>
> usb-storage: Error in queuecommand_lck: us->sfb= 8805bd61ccc0
>
> I did disc
Well, it is hard to say. rc2 without the patch showed more warnings,
but never crashed badly (queuecommand_lck).
The sample size is not big enough. maybe rc2 also has the
queuecommand_lck bug, but I havent hit it.
On Mon, Sep 1, 2014 at 12:37 PM, Mathias Nyman wrote:
> On 09/01/2014 12:36 PM
On 09/01/2014 01:26 PM, Ricardo Ribalda Delgado wrote:
> Well, it is hard to say. rc2 without the patch showed more warnings,
> but never crashed badly (queuecommand_lck).
>
> The sample size is not big enough. maybe rc2 also has the
> queuecommand_lck bug, but I havent hit it.
>
Ok, I won't
Do you have a NEC/Renesas uPD720200 USB 3.0 Host?
If so, try with an usb gadget acting as a mass storage. That hits the
bug in my machine.
Regarsd!
On Mon, Sep 1, 2014 at 1:12 PM, Mathias Nyman wrote:
> On 09/01/2014 01:26 PM, Ricardo Ribalda Delgado wrote:
>> Well, it is hard to say. rc2 witho
Hello Felipe
I think that you have forgotten about this patch :). It is needed by
usb3380 in usb3.0 mode. Otherwise the device keeps reseting.
Thanks!
On Tue, Aug 26, 2014 at 6:00 PM, Ricardo Ribalda Delgado
wrote:
> Without this patch, some hosts keep restarting indefinitely the target.
>
> Fi
On Mon, 01 Sep 2014, Octavian Purdila wrote:
> On Mon, Sep 1, 2014 at 12:51 PM, Lee Jones wrote:
> > On Mon, 01 Sep 2014, Octavian Purdila wrote:
> >
> >> On Mon, Sep 1, 2014 at 11:37 AM, Lee Jones wrote:
> >> > On Sat, 30 Aug 2014, Octavian Purdila wrote:
> >> >
> >> >> This patch implements th
Peter Bestler writes:
>
> I am using the g_printer driver in combination with kernel 3.2-rc7.
> The hardware-platform is a Freescale p2020 (devicecontroller is the
> fsl-usb2-core). For testing I use the printer.c-app in
> /Documentation/usb/gadget_printer.c
>
> After setting a correct configur
On 09/01/2014 02:19 PM, Ricardo Ribalda Delgado wrote:
> Do you have a NEC/Renesas uPD720200 USB 3.0 Host?
>
> If so, try with an usb gadget acting as a mass storage. That hits the
> bug in my machine.
>
Thanks for the tip, but currently I only got Intel hosts.
btw I earlier meant to say that I
I could offer you a net3380 usb gadget device (mini pcie or pcie) but
the uPD720200 is my notebook, so I cannot afford an extra one for you
:)
On Mon, Sep 1, 2014 at 2:25 PM, Mathias Nyman
wrote:
> On 09/01/2014 02:19 PM, Ricardo Ribalda Delgado wrote:
>> Do you have a NEC/Renesas uPD720200 USB 3
> On Sat, Aug 23, 2014 at 11:37:28PM +0800, peter li wrote:
>> 1.In which case will i get EPROTO during commuicate with usb device, i
>> called usb_bulk_msg in my usb_drv
>
> What driver is this?
>
I write the driver based on the old version usb-skeleton.c, the driver
works fine,the error EPROTO
I think I still miss a Signed-Off-By Felipe Balbi here...
All the rest should make it into 3.18, but USB without PHY is no fun to
use ;-)
Am 2014-08-19 01:37, schrieb Stefan Agner:
> This adds support for the USB PHY in Vybrid VF610. We assume that
> the disconnection without VBUS is also needed
Renesas USBHS controller support should be available only on
Renesas ARM SoCs and SuperH architecture.
Signed-off-by: Bartlomiej Zolnierkiewicz
Acked-by: Kyungmin Park
Cc: Simon Horman
Cc: Magnus Damm
---
drivers/usb/renesas_usbhs/Kconfig |1 +
1 file changed, 1 insertion(+)
Index: b/dri
Hello.
On 9/1/2014 5:14 PM, Bartlomiej Zolnierkiewicz wrote:
Renesas USBHS controller support should be available only on
Renesas ARM SoCs and SuperH architecture.
Signed-off-by: Bartlomiej Zolnierkiewicz
Acked-by: Kyungmin Park
Cc: Simon Horman
Cc: Magnus Damm
---
drivers/usb/renesas_
On Mon, 1 Sep 2014, Mathias Nyman wrote:
> On 09/01/2014 12:36 PM, Ricardo Ribalda Delgado wrote:
> > After some time of use (one hour or so) my system started to behave
> > "weird". I did check dmesg and I was receiving the following line
> > again and again:
> >
> > usb-storage: Error in queue
On Sun, 31 Aug 2014, S. Lockwood-Childs wrote:
> gadgetfs has had a module refcount bug in all recent kernels, from v3.10 up
> through present. I realize that gadgetfs is deprecated in favor of functionfs
> nowadays, but probably you will want to fix it anyways since gadgetfs is still
> in the tre
Renesas USBHS controller support should be available only on
Renesas ARM SoCs and SuperH architecture.
Signed-off-by: Bartlomiej Zolnierkiewicz
Acked-by: Kyungmin Park
Cc: Simon Horman
Cc: Magnus Damm
---
v2:
- s/ARCH_SH/SUPERH/ (thanks to Sergei Shtylyov)
drivers/usb/renesas_usbhs/Kconfig |
On Mon, 1 Sep 2014, peter li wrote:
> > On Sat, Aug 23, 2014 at 11:37:28PM +0800, peter li wrote:
> >> 1.In which case will i get EPROTO during commuicate with usb device, i
> >> called usb_bulk_msg in my usb_drv
> >
> > What driver is this?
> >
>
> I write the driver based on the old version us
On Mon, Sep 1, 2014 at 2:39 PM, Lee Jones wrote:
> On Mon, 01 Sep 2014, Octavian Purdila wrote:
>
>> On Mon, Sep 1, 2014 at 12:51 PM, Lee Jones wrote:
>> > On Mon, 01 Sep 2014, Octavian Purdila wrote:
>> >
>> >> On Mon, Sep 1, 2014 at 11:37 AM, Lee Jones wrote:
>> >> > On Sat, 30 Aug 2014, Octav
On Mon, 01 Sep 2014, Octavian Purdila wrote:
> On Mon, Sep 1, 2014 at 2:39 PM, Lee Jones wrote:
> > On Mon, 01 Sep 2014, Octavian Purdila wrote:
> >
> >> On Mon, Sep 1, 2014 at 12:51 PM, Lee Jones wrote:
> >> > On Mon, 01 Sep 2014, Octavian Purdila wrote:
> >> >
> >> >> On Mon, Sep 1, 2014 at 11
On Mon, Sep 1, 2014 at 6:46 PM, Lee Jones wrote:
> On Mon, 01 Sep 2014, Octavian Purdila wrote:
>
>> On Mon, Sep 1, 2014 at 2:39 PM, Lee Jones wrote:
>> > On Mon, 01 Sep 2014, Octavian Purdila wrote:
>> >
>> >> On Mon, Sep 1, 2014 at 12:51 PM, Lee Jones wrote:
>> >> > On Mon, 01 Sep 2014, Octavi
On Mon, Sep 1, 2014 at 4:24 PM, Bartlomiej Zolnierkiewicz
wrote:
> Renesas USBHS controller support should be available only on
> Renesas ARM SoCs and SuperH architecture.
>
> Signed-off-by: Bartlomiej Zolnierkiewicz
> Acked-by: Kyungmin Park
> Cc: Simon Horman
> Cc: Magnus Damm
> ---
> v2:
>
On Mon, Sep 01, 2014 at 07:22:39PM +0300, Octavian Purdila wrote:
> On Mon, Sep 1, 2014 at 6:46 PM, Lee Jones wrote:
> > On Mon, 01 Sep 2014, Octavian Purdila wrote:
> >
> >> On Mon, Sep 1, 2014 at 2:39 PM, Lee Jones wrote:
> >> > On Mon, 01 Sep 2014, Octavian Purdila wrote:
> >> >> On Mon, Sep 1
On Mon, Sep 01, 2014 at 06:40:50PM +0200, Geert Uytterhoeven wrote:
> On Mon, Sep 1, 2014 at 4:24 PM, Bartlomiej Zolnierkiewicz
> wrote:
> > Renesas USBHS controller support should be available only on
> > Renesas ARM SoCs and SuperH architecture.
> >
> > Signed-off-by: Bartlomiej Zolnierkiewicz
The variable "rx_buf_sz" is used by both tx and rx buffers. Replace
it with "agg_buf_sz".
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index cc6
From: Hayes Wang
Date: Tue, 2 Sep 2014 10:27:52 +0800
> The variable "rx_buf_sz" is used by both tx and rx buffers. Replace
> it with "agg_buf_sz".
>
> Signed-off-by: Hayes Wang
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord.
Dear all:
The kernel version is 3.16.1-1-ARCH
Today I keep getting this panic when booting up.
http://i.imgur.com/0Rx93Kr.jpg
It might be that the UAS device was in some strange state,
because that after I unplugged and power-cycled the UAS,
everything went normal again.
Does anyone know what's
Hi,
On 09/02/2014 06:18 AM, Chunwei Chen wrote:
> Dear all:
>
> The kernel version is 3.16.1-1-ARCH
>
> Today I keep getting this panic when booting up.
> http://i.imgur.com/0Rx93Kr.jpg
>
> It might be that the UAS device was in some strange state,
> because that after I unplugged and power-cyc
39 matches
Mail list logo
