Hi,
> -Original Message-
> From: Bhupesh SHARMA
> Sent: Wednesday, June 27, 2012 9:08 AM
> To: ba...@ti.com; linux-usb@vger.kernel.org
> Cc: gre...@linuxfoundation.org; laurent.pinch...@ideasonboard.com
> Subject: [RFC] usb: gadget: Ensure correct functionality for gadgets
> that wish to '
Hi,
On Thu, Jul 19, 2012 at 01:41:59PM +0530, Ajay Kumar Gupta wrote:
> Fixes endpoint starvation issue when more than one bulk QH is
> multiplexed on the reserved bulk TX endpoint.
>
> This patch sets the NAK timeout interval for such QHs, and when
> a timeout triggers the next QH will be schedu
Hi,
On Thu, Jul 19, 2012 at 05:15:57PM +0530, Ajay Kumar Gupta wrote:
> diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb_core.c
> index 89d1871..3e09984 100644
> --- a/drivers/usb/musb/musb_core.c
> +++ b/drivers/usb/musb/musb_core.c
> @@ -99,6 +99,7 @@
> #include
> #include
>
Hi,
On Thu, Jul 19, 2012 at 05:15:58PM +0530, Ajay Kumar Gupta wrote:
> Moved global variable "musb_debugfs_root" and static variable
> "old_state" to 'struct musb' to help support multi instance of
> musb controller as present on AM335x platform.
>
> Also removed the global variable "orig_dma_ma
Hi,
On Tue, Jul 24, 2012 at 09:08:40PM +0300, Ruslan Bilovol wrote:
> Currently this flag is not used anywhere and may be safely removed.
>
> Signed-off-by: Ruslan Bilovol
looks good to me. Keshava ?
> ---
> arch/arm/mach-omap2/usb-host.c|1 -
> arch/arm/plat-omap/include/plat/usb
Hello Sarah et. al,
I am attempting to use an Inland brand USB 3.0 multi-purpose Memory Card
reader, which I purchased from Micro Center, along with a Patriot EP Series
SDXC UHS-1 64 GB memory card, which I purchased from Fry's. I am connecting
these to my Debian unstable system running Linux 3
Hi,
> On Thu, Jul 19, 2012 at 01:41:59PM +0530, Ajay Kumar Gupta wrote:
> > Fixes endpoint starvation issue when more than one bulk QH is
> > multiplexed on the reserved bulk TX endpoint.
> >
> > This patch sets the NAK timeout interval for such QHs, and when
> > a timeout triggers the next QH will
Hi,
> On Thu, Jul 19, 2012 at 05:15:57PM +0530, Ajay Kumar Gupta wrote:
> > diff --git a/drivers/usb/musb/musb_core.c
> > b/drivers/usb/musb/musb_core.c index 89d1871..3e09984 100644
> > --- a/drivers/usb/musb/musb_core.c
> > +++ b/drivers/usb/musb/musb_core.c
> > @@ -99,6 +99,7 @@
> > #include
>
Hi,
>
> On Thu, Jul 19, 2012 at 05:15:58PM +0530, Ajay Kumar Gupta wrote:
> > Moved global variable "musb_debugfs_root" and static variable
> > "old_state" to 'struct musb' to help support multi instance of musb
> > controller as present on AM335x platform.
> >
> > Also removed the global variable
Hi,
> > On Thu, Jul 19, 2012 at 01:41:59PM +0530, Ajay Kumar Gupta wrote:
> > > Fixes endpoint starvation issue when more than one bulk QH is
> > > multiplexed on the reserved bulk TX endpoint.
> > >
> > > This patch sets the NAK timeout interval for such QHs, and when
> > > a timeout triggers the
On Wed, Jul 25, 2012 at 10:34:49AM +, Gupta, Ajay Kumar wrote:
> Hi,
> >
> > On Thu, Jul 19, 2012 at 05:15:58PM +0530, Ajay Kumar Gupta wrote:
> > > Moved global variable "musb_debugfs_root" and static variable
> > > "old_state" to 'struct musb' to help support multi instance of musb
> > > con
On Wed, Jul 25, 2012 at 10:38:59AM +, Gupta, Ajay Kumar wrote:
> Hi,
> > > On Thu, Jul 19, 2012 at 01:41:59PM +0530, Ajay Kumar Gupta wrote:
> > > > Fixes endpoint starvation issue when more than one bulk QH is
> > > > multiplexed on the reserved bulk TX endpoint.
> > > >
> > > > This patch set
Hi,
> On Wed, Jul 25, 2012 at 10:34:49AM +, Gupta, Ajay Kumar wrote:
> > Hi,
> > >
> > > On Thu, Jul 19, 2012 at 05:15:58PM +0530, Ajay Kumar Gupta wrote:
> > > > Moved global variable "musb_debugfs_root" and static variable
> > > > "old_state" to 'struct musb' to help support multi instance of
Hi Anton,
On Tue, July 17, 2012 9:27 pm, Anton Tikhomirov wrote:
> Hi,
>
>> -Original Message-
>> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
>> ow...@vger.kernel.org] On Behalf Of Ido Shayevitz
>> Sent: Thursday, July 12, 2012 1:24 AM
>> To: ba...@ti.com
>> Cc: linux-usb@vge
As NOP device node is now added in am33xx tree so remove the call
which creates the NOP platform_device.
Signed-off-by: Ajay Kumar Gupta
---
drivers/usb/musb/musb_dsps.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/musb/musb_dsps.c b/drivers/usb/musb/mus
AM33xx has two musb controller and they have one NOP PHY each.
Added the device tree data for NOP PHY.
Signed-off-by: Ajay Kumar Gupta
---
arch/arm/boot/dts/am33xx.dtsi |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/d
Added NOP PHY phandle to usbss device node as same will be used
to get the phy from otg framework.
Signed-off-by: Ajay Kumar Gupta
---
arch/arm/boot/dts/am33xx.dtsi |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.
Added device tree data for usbss on am33xx. There are two musb controllers
on am33xx platform so have port0_mode and port1_mode additional data.
Signed-off-by: Ajay Kumar Gupta
---
arch/arm/boot/dts/am33xx.dtsi | 11 +++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/a
Moved global variable "musb_debugfs_root" and static variable
"old_state" to 'struct musb' to help support multi instance of
musb controller as present on AM335x platform.
Also removed the global variable "orig_dma_mask" and filled the
dev->dma_mask with parent device's dma_mask.
Signed-off-by: A
Added 'id' field within 'struct musb' which can be used to determine
the current instance of musb controller.
Also defined musb_ida in musb_core.c to manage the core ids.
Signed-off-by: Ajay Kumar Gupta
---
drivers/usb/musb/am35x.c | 42 --
drivers/
This series of patches adds,
a) Multi instances support in musb driver
b) DT support for musb_dsps glue layer
c) DT support for NOP transceiver
AM33xx and TI81xx has dual musb controller and has two usb PHY of same type.
This patch series uses 'phandle' based API devm_usb_get_phy_by_phandle() to
g
AM33xx has two PHY of same type used by each musb controller so
use phandle of phy nodes to get the phy pointer.
Signed-off-by: Ajay Kumar Gupta
---
.../devicetree/bindings/usb/am33xx-usb.txt |2 ++
drivers/usb/musb/musb_dsps.c |4 +++-
2 files changed, 5 in
Currently we have one single nop transceiver support as same is
defined as a global variable in drivers/usb/otg/nop-usb-xceiv.c.
This need to be changed to support multiple otg controller each
using nop transceiver on a platform such as am335x.
Signed-off-by: Ajay Kumar Gupta
---
arch/arm/mach-o
Added device tree support for nop transceiver driver and updated the
Documentation with device tree binding information for am33xx platform.
Signed-off-by: Ajay Kumar Gupta
---
.../devicetree/bindings/usb/am33xx-usb.txt |3 +++
drivers/usb/otg/nop-usb-xceiv.c| 1
Added device tree support for dsps musb glue driver and updated the
Documentation with device tree binding information.
Signed-off-by: Ajay Kumar Gupta
---
.../devicetree/bindings/usb/am33xx-usb.txt | 14 +
drivers/usb/musb/musb_dsps.c | 60 +
AM335x and TI81xx platform has dual musb controller so updating the
musb_dspc.c to support the same.
Changes:
- Moved otg_workaround timer to glue structure
- Moved static local variable last_timer to glue structure
- PHY on/off related cleanups
Signed-off-by: Ajay Kumar G
Moved global variable "musb_debugfs_root" and static variable
"old_state" to 'struct musb' to help support multi instance of
musb controller as present on AM335x platform.
Also removed the global variable "orig_dma_mask" and filled the
dev->dma_mask with parent device's dma_mask.
Signed-off-by: A
Hi Balbi,
> -Original Message-
> From: Neil Zhang
> Sent: 2012年7月19日 22:48
> To: Neil Zhang; ba...@ti.com; gre...@linuxfoundation.org
> Cc: Chao Xie; khoroshi...@ispras.ru; linux-usb@vger.kernel.org
> Subject: RE: [PATCH 0/7 v2] usb: gadget: mv_udc: bug fix and feature
> add
>
> Hi Balbi,
hi,
On Wed, Jul 25, 2012 at 05:37:19PM +0530, Ajay Kumar Gupta wrote:
> diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb_core.c
> index 89d1871..f5eb8a7 100644
> --- a/drivers/usb/musb/musb_core.c
> +++ b/drivers/usb/musb/musb_core.c
> @@ -1889,6 +1921,7 @@ musb_init_controller
Hi,
>
> On Wed, Jul 25, 2012 at 05:37:19PM +0530, Ajay Kumar Gupta wrote:
> > diff --git a/drivers/usb/musb/musb_core.c
> > b/drivers/usb/musb/musb_core.c index 89d1871..f5eb8a7 100644
> > --- a/drivers/usb/musb/musb_core.c
> > +++ b/drivers/usb/musb/musb_core.c
>
>
>
> > @@ -1889,6 +1921,7 @@
Hi.
On Wed, Jul 25, 2012 at 12:19:32PM +, Gupta, Ajay Kumar wrote:
> Hi,
> >
> > On Wed, Jul 25, 2012 at 05:37:19PM +0530, Ajay Kumar Gupta wrote:
> > > diff --git a/drivers/usb/musb/musb_core.c
> > > b/drivers/usb/musb/musb_core.c index 89d1871..f5eb8a7 100644
> > > --- a/drivers/usb/musb/mu
Hi,
> On Wed, Jul 25, 2012 at 12:19:32PM +, Gupta, Ajay Kumar wrote:
> > Hi,
> > >
> > > On Wed, Jul 25, 2012 at 05:37:19PM +0530, Ajay Kumar Gupta wrote:
> > > > diff --git a/drivers/usb/musb/musb_core.c
> > > > b/drivers/usb/musb/musb_core.c index 89d1871..f5eb8a7 100644
> > > > --- a/drivers
On Wed, Jul 25, 2012 at 1:24 PM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Jul 24, 2012 at 09:08:40PM +0300, Ruslan Bilovol wrote:
>> Currently this flag is not used anywhere and may be safely removed.
>>
>> Signed-off-by: Ruslan Bilovol
>
> looks good to me. Keshava ?
Ruslan
please remove the
CC usb guys and list
On Wed, Jul 25, 2012 at 1:53 AM, Linus Torvalds
wrote:
>
> I really think the isight thing is a totally different thing entirely.
>
> And quite frankly, that's just a BUG in the USB implementation. If the
> USB ID changes, it shouldn't be considered a "resume" thing at all,
>
On Wed, Jul 25, 2012 at 12:30:12PM +, Gupta, Ajay Kumar wrote:
> Hi,
> > On Wed, Jul 25, 2012 at 12:19:32PM +, Gupta, Ajay Kumar wrote:
> > > Hi,
> > > >
> > > > On Wed, Jul 25, 2012 at 05:37:19PM +0530, Ajay Kumar Gupta wrote:
> > > > > diff --git a/drivers/usb/musb/musb_core.c
> > > > > b
Hi,
> On Wed, Jul 25, 2012 at 12:30:12PM +, Gupta, Ajay Kumar wrote:
> > Hi,
> > > On Wed, Jul 25, 2012 at 12:19:32PM +, Gupta, Ajay Kumar wrote:
> > > > Hi,
> > > > >
> > > > > On Wed, Jul 25, 2012 at 05:37:19PM +0530, Ajay Kumar Gupta wrote:
> > > > > > diff --git a/drivers/usb/musb/musb_
On Wednesday 25 July 2012 20:35:28 Ming Lei wrote:
> CC usb guys and list
>
> On Wed, Jul 25, 2012 at 1:53 AM, Linus Torvalds
> wrote:
> >
> > I really think the isight thing is a totally different thing entirely.
> >
> > And quite frankly, that's just a BUG in the USB implementation. If the
> >
This is first release of otg driver for the dwc3 Synopsys USB3 core.
The otg driver implements the otg final state machine and control the
activation of the device controller or host controller.
In this first implementation, only simple DRD mode is implemented,
determine if A or B device according
On Wed, Jul 25, 2012 at 8:43 PM, Oliver Neukum wrote:
> This is likely unwise. You'd better introduce a special flag for kernel
> threads
> that should be thawed only after user space will have been thawed.
IMO, it is not necessary to introduce one extra flag for the purpose since
- usermo
The short_not_ok field is used by class drivers to indicate udc whether short
packet is expected during a particular transfer.
In case of mass storage, during command and status phase this field is set as
false and set to true during data phase.
musb driver uses this field to decide whether to pr
On Wed, Jul 25, 2012 at 8:50 PM, Ming Lei wrote:
> - no harm to thaw all user space tasks before thawing all kernel threads
> (there isn't any dependency about the thawing order)
Sorry, I mean there isn't any constraint about the order, but the 'dependency'
may be just what the patch is
On Wed, 25 Jul 2012 14:53:00 +0200, Rajaram REGUPATHY
wrote:
The short_not_ok field is used by class drivers to indicate udc whether short
packet is expected during a particular transfer.
In case of mass storage, during command and status phase this field is set as
false and set to true durin
Hi Bhupesh,
On Wednesday 25 July 2012 15:06:37 Bhupesh SHARMA wrote:
[snip]
> It's been almost a month since this RFC was circulated.
> As no comments have been received so far,
http://www.spinics.net/lists/linux-usb/msg66755.html
Mails get lost sometime.
BTW, http://www.spinics.net/lists/lin
Hi, Bjorn,
Thank you very much for your detailed information.
On Wed, Jul 25, 2012 at 5:58 PM, Bjørn Mork wrote:
> Huang Ying writes:
>> On Wed, 2012-07-25 at 06:08 +0200, Bjørn Mork wrote:
>>> Enabling autosuspend for USB causes hotplug failure in the current
>>> linux-next. Newly plugged devi
Hi
On Wed, Jul 25, 2012 at 6:33 PM, Michal Nazarewicz wrote:
> On Wed, 25 Jul 2012 14:53:00 +0200, Rajaram REGUPATHY
> wrote:
>>
>> The short_not_ok field is used by class drivers to indicate udc whether
>> short packet is expected during a particular transfer.
>> In case of mass storage, during
huang ying writes:
> Hi, Bjorn,
>
> Thank you very much for your detailed information.
>
> On Wed, Jul 25, 2012 at 5:58 PM, Bjørn Mork wrote:
>> Huang Ying writes:
>>> On Wed, 2012-07-25 at 06:08 +0200, Bjørn Mork wrote:
Enabling autosuspend for USB causes hotplug failure in the current
>>
On Wed, 25 Jul 2012, Rajaram REGUPATHY wrote:
> The short_not_ok field is used by class drivers to indicate udc whether short
> packet is expected during a particular transfer.
> In case of mass storage, during command and status phase this field is set as
> false and set to true during data pha
On Wed, 25 Jul 2012, Rajaram R wrote:
> Hi
>
> On Wed, Jul 25, 2012 at 6:33 PM, Michal Nazarewicz wrote:
> > On Wed, 25 Jul 2012 14:53:00 +0200, Rajaram REGUPATHY
> > wrote:
> >>
> >> The short_not_ok field is used by class drivers to indicate udc whether
> >> short packet is expected during a
Add DT bindings to the ohci-pxa27x driver and some documentation.
Successfully tested on a PXA3xx board.
Signed-off-by: Daniel Mack
---
Documentation/devicetree/bindings/usb/pxa-usb.txt | 31 ++
drivers/usb/host/ohci-pxa27x.c| 68 +
2 files ch
Hi Laurent,
> -Original Message-
> From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
> Sent: Wednesday, July 25, 2012 6:41 PM
> To: Bhupesh SHARMA
> Cc: ba...@ti.com; linux-usb@vger.kernel.org; gre...@linuxfoundation.org
> Subject: Re: [RFC] usb: gadget: Ensure correct func
Hi Alan
On Wed, Jul 25, 2012 at 9:07 PM, Alan Stern wrote:
> On Wed, 25 Jul 2012, Rajaram R wrote:
>
>> Hi
>>
>> On Wed, Jul 25, 2012 at 6:33 PM, Michal Nazarewicz wrote:
>> > On Wed, 25 Jul 2012 14:53:00 +0200, Rajaram REGUPATHY
>> > wrote:
>> >>
>> >> The short_not_ok field is used by class d
On Wednesday 25 July 2012, Daniel Mack wrote:
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/pxa-usb.txt
> @@ -0,0 +1,31 @@
> +PXA USB controllers
> +
> +OHCI
> +
> +Required properties:
> + - compatible: Should be "mrvl,pxa-ohci" for USB controllers
> + used in host mode.
> +
> +
On Wed, 25 Jul 2012, Rajaram R wrote:
> >> > There's one thing I don't get. The message talks about musb but the code
> >> > checks for non Super Speed devices. So maybe the code is correct, maybe
> >> > it's not, but the message does not really explain it (at least to me).
> >> >
> >> Please le
On Wed, Jul 25, 2012 at 5:35 AM, Ming Lei wrote:
>
> The below patch should fix the problem above.
Actually, I think we could make this even simpler.
There's nothing wrong with saying "user mode is enabled" *just* before
we unthaw things, if we also simply guarantee that there is no
sleeping loc
On Wed, Jul 25, 2012 at 10:51 PM, Alan Stern wrote:
> On Wed, 25 Jul 2012, Rajaram R wrote:
>
>> >> > There's one thing I don't get. The message talks about musb but the
>> >> > code
>> >> > checks for non Super Speed devices. So maybe the code is correct, maybe
>> >> > it's not, but the messag
On Wed, Jul 25, 2012 at 02:31:20AM -0700, Matthew Hall wrote:
> Hello Sarah et. al,
Hi Matthew! It helps if you Cc my email address in your mail.
Otherwise it might get lost in a separate folder and ignored for a
couple days.
> I am attempting to use an Inland brand USB 3.0 multi-purpose Memory
When we encounter an xHCI host that needs the XHCI_TRUST_TX_LENGTH
quirk, the xHCI driver ends up spewing messages about the quirk into
dmesg every time a short packet occurs. Change the xHCI driver to
rate-limit such warnings.
This patch should be backported to kernels as old as 2.6.36, that
con
Hi Laurent,
> -Original Message-
> From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
> Sent: Saturday, July 07, 2012 6:37 PM
> To: Bhupesh SHARMA
> Cc: linux-usb@vger.kernel.org; ba...@ti.com; linux-
> me...@vger.kernel.org; gre...@linuxfoundation.org
> Subject: Re: [PATCH
Hi Laurent,
Sorry for the delayed reply. I thought of performing some extensive tests
before replying to your comments.
> -Original Message-
> From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
> Sent: Saturday, July 07, 2012 5:28 PM
> To: Bhupesh SHARMA
> Cc: linux-usb@vge
I'm not getting much traction with this approach. I get:
Turning light on now...[73405.001220] usb 1-1.2: usbfs: process 30710
(badusbled) did not claim interface 0 before use
libusb_control_transfer() returned -1
I'm not familiar enough with libusb to know what this error means.
--Adam
On
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of Alan Stern
>
> On Wed, 25 Jul 2012, Rajaram R wrote:
>
> > >> > There's one thing I don't get. The message talks about musb but
> > >> > the code checks for non Super Speed devices. So maybe the cod
On Wednesday, July 25, 2012, Bjørn Mork wrote:
> huang ying writes:
>
> > Hi, Bjorn,
> >
> > Thank you very much for your detailed information.
> >
> > On Wed, Jul 25, 2012 at 5:58 PM, Bjørn Mork wrote:
> >> Huang Ying writes:
> >>> On Wed, 2012-07-25 at 06:08 +0200, Bjørn Mork wrote:
> En
Got now, thanks.
On 07/25/2012 11:39 AM, Adam Wozniak wrote:
I'm not getting much traction with this approach. I get:
Turning light on now...[73405.001220] usb 1-1.2: usbfs: process 30710
(badusbled) did not claim interface 0 before use
libusb_control_transfer() returned -1
I'm not familia
On Wednesday, July 25, 2012, Linus Torvalds wrote:
> On Wed, Jul 25, 2012 at 5:35 AM, Ming Lei wrote:
> >
> > The below patch should fix the problem above.
>
> Actually, I think we could make this even simpler.
>
> There's nothing wrong with saying "user mode is enabled" *just* before
> we untha
On Wed, 25 Jul 2012, Rajaram R wrote:
> On Wed, Jul 25, 2012 at 10:51 PM, Alan Stern
> wrote:
> > On Wed, 25 Jul 2012, Rajaram R wrote:
> >
> >> >> > There's one thing I don't get. The message talks about musb but the
> >> >> > code
> >> >> > checks for non Super Speed devices. So maybe the c
If a PCI device is put into D3_cold by acpi_bus_set_power(),
the message printed by acpi_pci_set_power_state() says that its
power state has been changed to D4, which doesn't make sense.
In turn, if the device is put into D3_hot, the message says just
"D3" without specifying which variant of D3 it
On Wed, 25 Jul 2012, Paul Zimmerman wrote:
> > > > I don't understand this either. What's wrong with setting
> > > > short_not_ok while at SuperSpeed? It shouldn't force the use of a
> > bounce buffer.
> > > >
> > >
> > > I have just brought back some code removed by patch "usb: fix mass
> > > s
hello there,
i have an usb modem zte ev-do that i used with kernel from 2.6.29 up to 3.5.
since 3.5, i got the following message:
[77496.664090] usb 5-2: udev 10, busnum 5, minor = 521
[77496.664097] usb 5-2: New USB device found, idVendor=19d2, idProduct=
[77496.664102] usb 5-2: N
On Wednesday, July 25, 2012, Bjørn Mork wrote:
> huang ying writes:
>
> > Hi, Bjorn,
> >
> > Thank you very much for your detailed information.
> >
> > On Wed, Jul 25, 2012 at 5:58 PM, Bjørn Mork wrote:
> >> Huang Ying writes:
> >>> On Wed, 2012-07-25 at 06:08 +0200, Bjørn Mork wrote:
> En
On Wed, 25 Jul 2012, Rafael J. Wysocki wrote:
>
> If a PCI device is put into D3_cold by acpi_bus_set_power(),
> the message printed by acpi_pci_set_power_state() says that its
> power state has been changed to D4, which doesn't make sense.
> In turn, if the device is put into D3_hot, the message
Cc: Matthieu CASTET
Cc: Stanislaw Gruszka
Cc: Greg Kroah-Hartman
Cc: linux-usb@vger.kernel.org
Signed-off-by: Tim Gardner
---
drivers/usb/atm/ueagle-atm.c | 79 +++---
1 file changed, 66 insertions(+), 13 deletions(-)
diff --git a/drivers/usb/atm/ueagle-a
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: Wednesday, July 25, 2012 12:48 PM
> To: Paul Zimmerman
> Cc: Rajaram R; Michal Nazarewicz; linux-usb@vger.kernel.org
> Subject: RE: usb : mass storage : short_not_ok for non usb3 udc
>
> On Wed, 25 Jul 2012, Paul Zimmerman wrote:
>
> >
On Wednesday, July 25, 2012, Alan Stern wrote:
> On Wed, 25 Jul 2012, Rafael J. Wysocki wrote:
>
> >
> > If a PCI device is put into D3_cold by acpi_bus_set_power(),
> > the message printed by acpi_pci_set_power_state() says that its
> > power state has been changed to D4, which doesn't make sens
On Wed, 25 Jul 2012, Paul Zimmerman wrote:
> > From: Alan Stern [mailto:st...@rowland.harvard.edu]
> > Sent: Wednesday, July 25, 2012 12:48 PM
> > To: Paul Zimmerman
> > Cc: Rajaram R; Michal Nazarewicz; linux-usb@vger.kernel.org
> > Subject: RE: usb : mass storage : short_not_ok for non usb3 udc
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: Wednesday, July 25, 2012 2:03 PM
>
> On Wed, 25 Jul 2012, Paul Zimmerman wrote:
>
> > > From: Alan Stern [mailto:st...@rowland.harvard.edu]
> > > Sent: Wednesday, July 25, 2012 12:48 PM
> > > To: Paul Zimmerman
> > > Cc: Rajaram R; Mic
On Wed, Jul 25, 2012 at 12:51:34PM -0700, nirinA raseliarison wrote:
> hello there,
> i have an usb modem zte ev-do that i used with kernel from 2.6.29 up to 3.5.
> since 3.5, i got the following message:
>
> [77496.664090] usb 5-2: udev 10, busnum 5, minor = 521
> [77496.664097] usb 5-2:
On Sun, Jul 22, 2012 at 05:28:12PM +0200, Yann Cantin wrote:
> /***
> * sysfs part
> */
>
> /*
> * screen min/max and H matrix coefs
> * _get return *current* value
> * _set set new value
> */
> #define DEVICE_MINMAX
"Rafael J. Wysocki" writes:
> This is not really necessary. The problem is the change of behavior I was
> worried about some time ago.
>
> Namely, the device in question apparently doesn't support ACPI D3_hot,
> so acpi_pm_device_sleep_state() returns D2 as the target state, where it
> would ret
On Sun, Jul 22, 2012 at 07:35:58PM +0200, Marian Beermann wrote:
> Hi,
>
> I have here a "Microsoft Sidewinder Strategic Commander". It's
> basically a fancy joystick (two axis plus rotation and a dozen or so
> buttons), but it's not HID compliant, i.e. I can only use it via
> hidraw.
> I already
Hi Bhupesh,
On Thursday 26 July 2012 00:12:46 Bhupesh SHARMA wrote:
> On Wednesday, July 25, 2012 6:41 PM Laurent Pinchart wrote:
> > On Wednesday 25 July 2012 15:06:37 Bhupesh SHARMA wrote:
> >
> > [snip]
> >
> > > It's been almost a month since this RFC was circulated.
> > > As no comments hav
The following changes since commit 84a1caf1453c3d44050bd22db958af4a7f99315c:
Linux 3.5-rc7 (2012-07-14 15:40:28 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-3.6-rc1
for you to fetch changes up to e387ef5c47ddeaeaa3cbdc
On Thu, Jul 26, 2012 at 1:23 AM, Linus Torvalds
wrote:
>
> So *if* the only problem wrt the USB hub code comes from this area,
IMO, USB hub code may not be the only one because both device_add and
device_del can just be run in process context, so any hotplug bus
may have this kind of problem sin
Hi Ido,
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of Ido Shayevitz
> Sent: Wednesday, July 25, 2012 9:46 PM
> To: ba...@ti.com; av.tikhomi...@samsung.com
> Cc: linux-usb@vger.kernel.org; i...@codeaurora.org
> Subject:
Hi, Rafael,
On Wed, 2012-07-25 at 22:02 +0200, Rafael J. Wysocki wrote:
> On Wednesday, July 25, 2012, Bjørn Mork wrote:
> > huang ying writes:
> >
> > > Hi, Bjorn,
> > >
> > > Thank you very much for your detailed information.
> > >
> > > On Wed, Jul 25, 2012 at 5:58 PM, Bjørn Mork wrote:
> >
On Thu, 2012-07-26 at 00:36 +0200, Bjørn Mork wrote:
> "Rafael J. Wysocki" writes:
>
> > This is not really necessary. The problem is the change of behavior I was
> > worried about some time ago.
> >
> > Namely, the device in question apparently doesn't support ACPI D3_hot,
> > so acpi_pm_device
This patchset addresses a few issues found out while enumerating/running
USBCV's UVC test suite with the UVC webcam gadget.
After these fixes, all the UVC related test assertions PASS (but
one also need to handle the Processing Unit/Selector Unit and Camera
Terminal Unit test cases in the applicat
In case of super-speed descriptors for a UVC device, the `bEndpointAddress` of
the video control endpoint (interrupt endpoint), was not correctly
assigned and hence it was initialized with a default value of 0x80.
This caused the enumeration of a super-speed UVC device on a Windows7
host machine to
As per UVC compliance test specification's assertion number 6.3.90
related to 'Standard VS Isochronous Video Data Endpoint Descriptor Assertions',
the bits D3..2 of 'bmAttributes' field of Standard VS Isochronous Video Data
Endpoint Descriptor should be 01 (binary) to indicate that the
synchronizat
As per the UVC compliance test suite's assertion 6.1.25, the `iFunction`
field of the Interface Association Descriptor (IAD) should the match the
`iInterface` field of the standard Video Control (VC) Interface Descriptor for
this Video Interface Collection (VIC).
This mandatory case is captured in
On Wed, Jul 25, 2012 at 10:46:37AM -0700, Sarah Sharp wrote:
> Hi Matthew! It helps if you Cc my email address in your mail.
> Otherwise it might get lost in a separate folder and ignored for a
> couple days.
I was attempting to follow the pattern you established with Gary when you
redirected hi
Forgot to mention, I put a new log here with the latest behavior with the
patch:
http://www.mhcomputing.net/tmp/xhci-bug/dmesg-usb-3-port-quirk-patch-plugin.txt.gz
Regards,
Matthew.
On Wed, Jul 25, 2012 at 10:24:26PM -0700, Matthew Hall wrote:
> On Wed, Jul 25, 2012 at 10:46:37AM -0700, Sarah S
On Thu, Jul 26, 2012 at 2:33 AM, Alan Stern wrote:
> On Wed, 25 Jul 2012, Paul Zimmerman wrote:
>
>> > From: Alan Stern [mailto:st...@rowland.harvard.edu]
>> > Sent: Wednesday, July 25, 2012 12:48 PM
>> > To: Paul Zimmerman
>> > Cc: Rajaram R; Michal Nazarewicz; linux-usb@vger.kernel.org
>> > Subj
After sending the USB Bus reset, Host waits for High Speed Chirps.
If the soft-disconnect and soft-connect happens during this chirp time,
then Host doesn't detect this disconnect.
Host treats this as Full Speed Device as there are no chirps.
To avoid this Full Speed Enumeration, soft-disconnect an
After sending the USB Bus reset, Host waits for High Speed Chirps.
If the soft-disconnect and soft-connect happens during this chirp time,
then Host doesn't detect this disconnect.
Host treats this as Full Speed Device as there are no chirps.
To avoid this Full Speed Enumeration, soft-disconnect an
94 matches
Mail list logo
