Re: [PATCH 18/21] usb/gadget: remove string override from struct usb_composite_driver

On 08/29/2012 10:58 PM, Michal Nazarewicz wrote: @@ -1625,8 +1612,6 @@ int usb_composite_probe(struct usb_composite_driver *driver) if (!driver->name) driver->name = "composite"; - if (!driver->iProduct) - driver->iProduct = driver->name; This leave

Re: [PATCH 19/21] usb/gadget: Provide a default implementation of default manufacturer string

On 08/29/2012 11:05 PM, Michal Nazarewicz wrote: Sebastian Andrzej Siewior writes: Some gadgets provide custom entry here. Some may override it with an etntry that is also created by composite if there was no value sumbitted at all. This patch removes all "custom manufacturer" strings which are

[PATCH 19/21 v2] usb/gadget: Provide a default implementation of default manufacturer string

Some gadgets provide custom entry here. Some may override it with an etntry that is also created by composite if there was no value sumbitted at all. This patch removes all "custom manufacturer" strings which are the same as these which are created by composite. Then it moves the creation of the de

Re: [PATCH 18/21 v2] usb/gadget: remove string override from struct usb_composite_driver

The struct usb_composite_driver members iProduct, iSerial and iManufacturer can be entered directly via the string array. There is no need for them to appear here. Signed-off-by: Sebastian Andrzej Siewior --- v1..v2: initialize iProduct with proper id drivers/usb/gadget/composite.c| 29 ++

Re: JMicron 20337 (152d:2338) and 3TB

Hello, Is there anything new in this regard? I have the same issue with 3T drive. Thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [RFC] usb/dummy_hcd: use -ESHUTDOWN if an URB can not be assigned to an UDC EP

* Alan Stern | 2012-08-29 13:31:54 [-0400]: >On Wed, 29 Aug 2012, Sebastian Andrzej Siewior wrote: >> --- a/drivers/net/usb/usbnet.c >> +++ b/drivers/net/usb/usbnet.c >> @@ -194,6 +194,7 @@ static void intr_complete (struct urb *urb) >> /* software-driven interface shutdown */ >> case -E

[PATCH v8 13/13] usb: otg: nop: add dt support

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 Signed-off-by: Ravi Babu --- .../devicetree/bindings/usb/am33xx-usb.txt |3 +++ drivers/usb/otg/nop-usb-xceiv.

[PATCH v8 07/13] usb: musb: dsps: add dt support

From: Ajay Kumar Gupta Added device tree support for dsps musb glue driver and updated the Documentation with device tree binding information. Signed-off-by: Ajay Kumar Gupta Signed-off-by: Ravi Babu Signed-off-by: Santhapuri, Damodar Signed-off-by: Ravi Babu --- .../devicetree/bindings/usb

[PATCH v8 05/13] usb: musb: am335x: add support for dual instance

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

[PATCH v8 04/13] usb: musb: kill global and static for multi instance

From: Ajay Kumar Gupta 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 dm

[PATCH v8 01/13] usb: musb: dsps: add phy control logic to glue

From: Santhapuri, Damodar AM335x uses NOP transceiver driver and need to enable builtin PHY by writing into usb_ctrl register available in system control module register space. This is being added at musb glue driver layer untill a separate system control module driver is available. Signed-off-b

[PATCH v8 00/13] usb: musb: adding multi instance support

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

[PATCH v8 02/13] usb: musb: dsps: enable phy control for am335x

From: Ajay Kumar Gupta Enabled the phy control logic for am335x also based on usbss revision register. Signed-off-by: Ajay Kumar Gupta Signed-off-by: Santhapuri, Damodar Signed-off-by: Ravi Babu --- arch/arm/plat-omap/include/plat/usb.h |1 + drivers/usb/musb/musb_dsps.c | 17

[PATCH v8 08/13] arm/dts: am33xx: Add dt data for usbss

From: Ajay Kumar Gupta 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 Signed-off-by: Ravi Babu Signed-off-by: Santhapuri, Damodar Signed-off-by: Ravi Babu --- ar

[PATCH v8 10/13] usb: musb: dsps: remove explicit NOP device creation

From: Ajay Kumar Gupta 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 Signed-off-by: Ravi Babu Signed-off-by: Santhapuri, Damodar Signed-off-by: Ravi Babu --- drivers/usb/musb/musb_dsps.c |3 +-- 1

[PATCH v8 03/13] usb: musb: add musb_ida for multi instance support

Added musb_ida in musb_core.c to manage the multi core ids. Signed-off-by: Ajay Kumar Gupta Signed-off-by: Ravi Babu Signed-off-by: Santhapuri, Damodar Signed-off-by: Ravi Babu --- drivers/usb/musb/am35x.c | 42 -- drivers/usb/musb/blackfin.c |

[PATCH v8 11/13] usb: musb: dsps: get the PHY using phandle api

From: Santhapuri, Damodar 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 Signed-off-by: Ravi Babu Signed-off-by: Santhapuri, Damodar Signed-off-by: Ravi Babu --- .../devicetree/bindings/usb/am3

[PATCH v8 09/13] arm/dts: am33xx: add dt data for usb nop phy

From: Ajay Kumar Gupta 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 Signed-off-by: Ravi Babu Signed-off-by: Santhapuri, Damodar Signed-off-by: Ravi Babu --- arch/arm/boot/dts/am33xx.dtsi |8 +++

[PATCH v8 06/13] usb: otg: nop: add support for multiple tranceiver

From: Santhapuri, Damodar 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

[PATCH v8 12/13] arm/dts: am33xx: add phy phandle to usbss

From: Ajay Kumar Gupta 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 Signed-off-by: Ravi Babu Signed-off-by: Santhapuri, Damodar Signed-off-by: Ravi Babu --- arch/arm/boot/dts/am33xx.dtsi |2 ++ 1 files

Re: [PATCH v8 08/13] arm/dts: am33xx: Add dt data for usbss

Hello. On 30-08-2012 14:50, Ravi Babu wrote: From: Ajay Kumar Gupta 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 Signed-off-by: Ravi Babu Signed-off-by: S

Re: [PATCH 18/21 v2] usb/gadget: remove string override from struct usb_composite_driver

Sebastian Andrzej Siewior writes: > The struct usb_composite_driver members iProduct, iSerial and > iManufacturer can be entered directly via the string array. There is no > need for them to appear here. > > Signed-off-by: Sebastian Andrzej Siewior Acked-by: Michal Nazarewicz -- Best regards,

Re: [PATCH 19/21 v2] usb/gadget: Provide a default implementation of default manufacturer string

Sebastian Andrzej Siewior writes: > Some gadgets provide custom entry here. Some may override it with an > etntry that is also created by composite if there was no value sumbitted > at all. > This patch removes all "custom manufacturer" strings which are the same > as these which are created by co

[PATCH] usb: otg: mxs-phy: Fix mx23 operation

From: Mike Thompson Currently mx23 fails to enumerate a USB device: [ 1.30] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1.52] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1.74] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1.96] hub 1-0:1.0: unabl

[PATCH 2/2] usb: otg: mxs-phy: Improve mxs phy initialization

From: Mike Thompson Improve error reporting for USB device reset and initialization. Add device definitions for proper use of the clear register with the specific bits required to power up the USB device upon initialization and to power down upon shutdown. Signed-off-by: Mike Thompson Signed-o

Re: detected XactErr

On Wed, 29 Aug 2012, Gary E. Miller wrote: > Yo Alan! > > On Wed, 29 Aug 2012 17:08:43 -0400 (EDT) > Alan Stern wrote: > > > > Uh, not easy. This is a production machine. Acceptable downtime is > > > very small. There should be a way to turn it off at runtime. > > > > No, there shouldn't.

[PATCH 1/2] usb: otg: mxs-phy: Fix mx23 operation

From: Mike Thompson Currently mx23 fails to enumerate a USB device: [ 1.30] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1.52] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1.74] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1.96] hub 1-0:1.0: unabl

Re: How to associate lsusb bus/device with /dev entry?

Just out of curiosity... Why did you post two nearly identical versions of this message? On Wed, 29 Aug 2012, Mathew Binkley wrote: > Hi all. How can you associate a USB Bus:Device info with a /dev/entry? There is no general way to do this because most USB devices don't have entries under /d

Re: [RFC PATCH 2/2] USB: Set usb port's DevicerRemovable according acpi information in EHCI

On Thu, 30 Aug 2012, Lan Tianyu wrote: > OK. This can resolve the root hub problems. And this let me think of the > same problem for non-root hub on the motherboard(e.g ehci has integrated > hub under root hub). Their ports also have acpi information. > I think we also need to find some place to s

Re: [RFC] usb/dummy_hcd: use -ESHUTDOWN if an URB can not be assigned to an UDC EP

On Thu, 30 Aug 2012, Sebastian Andrzej Siewior wrote: > >So the problem appears to be that dummy-hcd doesn't implement the right > >interval for periodic transfers. I'd accept a patch to fix that. > > That is also missing. However, we are pulled down, that means > find_endpoint() in dummy retur

Re: JMicron 20337 (152d:2338) and 3TB

On Thu, 30 Aug 2012, Alon Bar-Lev wrote: > Hello, > > Is there anything new in this regard? > I have the same issue with 3T drive. What are you referring to? What issue? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vg

Re: [RFC PATCH 2/2] USB: Set usb port's DevicerRemovable according acpi information in EHCI

On 2012年8月30日 22:21:15, Alan Stern wrote: Yes. Here you probably want the ACPI information to override the information provided by the integrated hub's hub descriptor. You can do this from within hub_configure(), at the point where you were going to add the second call to get_hub_descriptor().

Re: Virtualbox/Vmware usb device is working but on installed linux not.

Please use Reply-To-All so that your messages get sent to the mailing list as well as to me. On Thu, 30 Aug 2012, adam ? wrote: > Ok my friend have the same error. Will be this patch added to new kernel? I will submit it. By the way, what is a Joss Optical device? What does it do? Alan Stern

Re: [PATCH] OMAP: USB : Fix the EHCI enumeration and core retention issue

Munegowda, Keshava writes: > >> usb host retention in idle is not supported till now. > > when we see the usb bus suspend, then we disable the clocks of usb host to > enable to enable the retention in cpu idle; since we have disabled the clock > of > usb host , we will not see the device connec

Re: [RFC] usb/dummy_hcd: use -ESHUTDOWN if an URB can not be assigned to an UDC EP

On 08/30/2012 04:28 PM, Alan Stern wrote: On Thu, 30 Aug 2012, Sebastian Andrzej Siewior wrote: So the problem appears to be that dummy-hcd doesn't implement the right interval for periodic transfers. I'd accept a patch to fix that. That is also missing. However, we are pulled down, that mea

Re: How to associate lsusb bus/device with /dev entry?

On 08/30/2012 09:18 AM, Alan Stern wrote: Just out of curiosity... Why did you post two nearly identical versions of this message? I subscribed to the email list yesterday, sent my message 5 minutes later, and after I'd sent it Majordomo sent me an email requiring me to send a confirmation

Re: [PATCH 1/2] usb: otg: mxs-phy: Fix mx23 operation

Dear Fabio Estevam, > From: Mike Thompson > > Currently mx23 fails to enumerate a USB device: > > [ 1.30] hub 1-0:1.0: unable to enumerate USB device on port 1 > [ 1.52] hub 1-0:1.0: unable to enumerate USB device on port 1 > [ 1.74] hub 1-0:1.0: unable to enumerate USB device on po

Re: [RFC PATCH 2/2] USB: Set usb port's DevicerRemovable according acpi information in EHCI

On Thu, 30 Aug 2012, Lan Tianyu wrote: > On 2012年8月30日 22:21:15, Alan Stern wrote: > > Yes. Here you probably want the ACPI information to override the > > information provided by the integrated hub's hub descriptor. > > > > You can do this from within hub_configure(), at the point where you > >

Re: How to associate lsusb bus/device with /dev entry?

On Thu, 30 Aug 2012, Mathew Binkley wrote: > On 08/30/2012 09:18 AM, Alan Stern wrote: > > > Just out of curiosity... Why did you post two nearly identical > > versions of this message? > > I subscribed to the email list yesterday, sent my message 5 minutes > later, and after I'd sent it Major

Re: [RFC] usb/dummy_hcd: use -ESHUTDOWN if an URB can not be assigned to an UDC EP

On Thu, 30 Aug 2012, Sebastian Andrzej Siewior wrote: > > You're missing the point. The test of the interrupt URB's interval > > should be done _before_ find_endpoint() is called. > > The endpoint has a last_io field which could be used for that (which > isn't used right now at all) so I though

Re: [PATCH] usb: dwc3: correct default value of maxburst

On Thu, Aug 30, 2012 at 11:19:15AM +0900, Chanho Park wrote: > > -Original Message- > > From: Felipe Balbi [mailto:ba...@ti.com] > > Sent: Thursday, August 30, 2012 1:15 AM > > To: Chanho Park > > Cc: ba...@ti.com; linux-usb@vger.kernel.org; gre...@linuxfoundation.org; > > Kyungmin Park > >

Re: [PATCHv2] usb: dwc3: correct default value of maxburst

On Thu, Aug 30, 2012 at 11:58:59AM +0900, Chanho Park wrote: > This patch changes default value of maxburst to 1. When a connection is > established to highspeed not superspeed, the maxburst is set to 0. > So, we need to check and change default value of the maxburst before setting > up > burst si

Re: create libcomposite, v3

On Wed, Aug 29, 2012 at 10:53:33AM -0700, Greg KH wrote: > On Wed, Aug 29, 2012 at 07:13:45PM +0200, Sebastian Andrzej Siewior wrote: > > This series creates the libcomposite and is based on "Towords libcomposite, > > v2" > > It addresses the review comments of "create libcomposite". > > > > The

Re: [PATCH 1/2] usb: otg: mxs-phy: Fix mx23 operation

Hi Marek, On Thu, Aug 30, 2012 at 12:20 PM, Marek Vasut wrote: > >> +#define MXY_PHY_ENHOSTDISCONDETECT_DELAY 250 >> + > > Why 250 ? :) It is 250 ms. We found this one to be a safe value to enable ENHOSTDISCONDETECT in our tests. >> + /* >> + * Delay enabling ENHOSTDISCONDETECT so

Re: JMicron 20337 (152d:2338) and 3TB

On Thu, Aug 30, 2012 at 5:29 PM, Alan Stern wrote: > > On Thu, 30 Aug 2012, Alon Bar-Lev wrote: > > > Hello, > > > > Is there anything new in this regard? > > I have the same issue with 3T drive. > > What are you referring to? What issue? > > Alan Stern > Thanks for replying! This[1] thread. I

Re: [PATCH 1/2] usb: otg: mxs-phy: Fix mx23 operation

Dear Fabio Estevam, > Hi Marek, > > On Thu, Aug 30, 2012 at 12:20 PM, Marek Vasut wrote: > >> +#define MXY_PHY_ENHOSTDISCONDETECT_DELAY 250 > >> + > > > > Why 250 ? :) > > It is 250 ms. We found this one to be a safe value to enable > ENHOSTDISCONDETECT in our tests. Documentation / comm

Re: JMicron 20337 (152d:2338) and 3TB

On Thu, 30 Aug 2012, Alon Bar-Lev wrote: > On Thu, Aug 30, 2012 at 5:29 PM, Alan Stern wrote: > > > > On Thu, 30 Aug 2012, Alon Bar-Lev wrote: > > > > > Hello, > > > > > > Is there anything new in this regard? > > > I have the same issue with 3T drive. > > > > What are you referring to? What iss

Re: JMicron 20337 (152d:2338) and 3TB

On Thu, Aug 30, 2012 at 9:49 PM, Alan Stern wrote: > On Thu, 30 Aug 2012, Alon Bar-Lev wrote: > >> On Thu, Aug 30, 2012 at 5:29 PM, Alan Stern >> wrote: >> > >> > On Thu, 30 Aug 2012, Alon Bar-Lev wrote: >> > >> > > Hello, >> > > >> > > Is there anything new in this regard? >> > > I have the sam

Re: JMicron 20337 (152d:2338) and 3TB

On Thu, 30 Aug 2012, Alon Bar-Lev wrote: > On Thu, Aug 30, 2012 at 9:49 PM, Alan Stern wrote: > > On Thu, 30 Aug 2012, Alon Bar-Lev wrote: > > > >> On Thu, Aug 30, 2012 at 5:29 PM, Alan Stern > >> wrote: > >> > > >> > On Thu, 30 Aug 2012, Alon Bar-Lev wrote: > >> > > >> > > Hello, > >> > > > >>

Re: JMicron 20337 (152d:2338) and 3TB

On Thu, Aug 30, 2012 at 11:28 PM, Alan Stern wrote: > On Thu, 30 Aug 2012, Alon Bar-Lev wrote: > >> On Thu, Aug 30, 2012 at 9:49 PM, Alan Stern >> wrote: >> > On Thu, 30 Aug 2012, Alon Bar-Lev wrote: >> > >> >> On Thu, Aug 30, 2012 at 5:29 PM, Alan Stern >> >> wrote: >> >> > >> >> > On Thu, 30

Re: JMicron 20337 (152d:2338) and 3TB

On Thu, 30 Aug 2012, Alon Bar-Lev wrote: > Thank you! > > I will test this and report back. > > As this is in scsi layer, I guess it does not get the USB > vendor:product to automatically apply this workaround... :( I don't entirely understand this comment. But it is true that the patch will a

Re: JMicron 20337 (152d:2338) and 3TB

On Thu, Aug 30, 2012 at 11:47 PM, Alan Stern wrote: > On Thu, 30 Aug 2012, Alon Bar-Lev wrote: > >> Thank you! >> >> I will test this and report back. >> >> As this is in scsi layer, I guess it does not get the USB >> vendor:product to automatically apply this workaround... :( > > I don't entirely

Re: JMicron 20337 (152d:2338) and 3TB

On Thu, 30 Aug 2012, Alon Bar-Lev wrote: > I was trying to figure out if there can be automatic workaround based > on USB vendor:product... If these exposed at this point then a patch > can be written to effect only this device. > > I never traced the scsi module, but scsi_device does contain ven

[PATCH v2 1/2] usb: otg: mxs-phy: Fix mx23 operation

From: Mike Thompson Currently mx23 fails to enumerate a USB device: [ 1.30] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1.52] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1.74] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1.96] hub 1-0:1.0: unabl

[PATCH] ftdi_sio: PID for NZR SEM 16+ USB

This adds the USB PID for the NZR SEM 16+ USB energy monitor device . It works perfectly with the GPL software on . Signed-off-by: Horst Schirmeier --- drivers/usb/serial/ftdi_sio.c |1 + drivers/usb/serial/ftdi_sio_ids.h |3 +++

Re: create libcomposite, v3

On Wed, Aug 29, 2012 at 12:35 PM, Sebastian Andrzej Siewior wrote: > On 08/29/2012 08:36 PM, Greg KH wrote: >> >> I'd be glad to remove that code, if the Android people say they no >> longer need it. Last I heard, their userspace code needed to be changed >> over, and the Samsung developers were

RE: [PATCH] usb: dwc3: correct default value of maxburst

> -Original Message- > From: Felipe Balbi [mailto:ba...@ti.com] > Sent: Friday, August 31, 2012 12:51 AM > To: Chanho Park > Cc: ba...@ti.com; linux-usb@vger.kernel.org; gre...@linuxfoundation.org; > 'Kyungmin Park' > Subject: Re: [PATCH] usb: dwc3: correct default value of maxburst > > On

[PATCHv3] usb: dwc3: use a burst size only ss-mode

When connection is established non-ss mode, a maxburst is set to 0. Therefore, the value of burst size has wrong value. We must use the burst size only in ss-mode. Signed-off-by: Chanho Park Signed-off-by: Kyungmin Park --- drivers/usb/dwc3/gadget.c |6 +- 1 file changed, 5 insertions(+

Re: JMicron 20337 (152d:2338) and 3TB

On 05/08/2012 06:12 PM, Norman Diamond wrote: On Wed, 2012/5/9, Alan Stern wrote: On Tue, 8 May 2012, Norman Diamond wrote: Alan Stern wrote: On Tue, 8 May 2012, Norman Diamond wrote: In my case there is no other way that a host (PC or other, any OS or driver) could obtain a reported capaci

[PATCH v2] usb: move phy driver from mach-tegra to drivers/usb

As part of this patch: 1. Moved existing tegra phy driver to drivers/USB directory. 2. Added standard USB phy driver APIs to tegra phy driver. Signed-off-by: Venu Byravarasu --- delta from v1: 1. Used standard USB phy driver APIs 2. Restored ULPI phy support, which was removed in