Re: [PATCHv2 / RESEND 2/2] usb: storage: scsiglue: limit USB3 devices to 2048 sectors

Hi, Alan Stern writes: >> diff --git a/drivers/usb/storage/usb.c b/drivers/usb/storage/usb.c >> index 43576ed31ccd..b7735c9850f8 100644 >> --- a/drivers/usb/storage/usb.c >> +++ b/drivers/usb/storage/usb.c >> @@ -594,6 +594,10 @@ static int get_device_info(struct

Re: PROBLEM: Mouse connected to USB-3 stopped working 2.6.38->39 regression

Alan Stern writes: > > On Mon, 25 Apr 2011, Thomas Lindroth wrote: > > > On 04/23/2011 10:17 PM, Alan Stern wrote: > > > On Sat, 23 Apr 2011, Thomas Lindroth wrote: > > >> On 04/23/2011 05:31 PM, Alan Stern wrote: > > >>> Your separate post didn't include the dmesg showing what

Re: [PATCH v6 01/12] usb: hcd: Initialize hcd->flags to 0

On Thu, Apr 07, 2016 at 01:40:21PM +0300, Roger Quadros wrote: > On 07/04/16 12:42, Peter Chen wrote: > > On Wed, Apr 06, 2016 at 09:32:22AM +0300, Roger Quadros wrote: > >> On 06/04/16 09:09, Felipe Balbi wrote: > >>> > >>> Hi, > >>> > >>> Roger Quadros writes: > diff --git

我的相片在

你的老朋友邀你来Q群:343257759 抢红包 抢秒杀 抢vip 什么都要抢。太刺激了。不靠手气只拼手速

Re: [RFT PATCH 0/4] usb: dwc2: Fix core reset and force mode delay problems

On 4/4/2016 3:51 AM, Felipe Balbi wrote: > > Hi John, > > John Youn writes: >> The following patch series addresses the core reset and force mode >> delay problems we have been seeing on dwc2 for some platforms. >> >> I think I have identified the source of the

Re: [RFT PATCH 0/4] usb: dwc2: Fix core reset and force mode delay problems

On 4/7/2016 1:36 PM, Michael Niewoehner wrote: > > Am 07.04.2016 um 20:41 schrieb John Youn : > >> On 3/31/2016 2:44 PM, Michael Niewoehner wrote: >>> Hi John, >>> >>> Am 29.03.2016 um 04:36 schrieb John Youn : >>> Hi, The following

Re: [PATCH] usb: f_mass_storage: test whether thread is running before starting another

Hi, On 7.04.2016 17:46, Ivaylo Dimitrov wrote: Hi, On 7.04.2016 17:25, Alan Stern wrote: On Thu, 7 Apr 2016, Michal Nazarewicz wrote: Sounds good to me. I’d love someone to test this patch (I sadly have no way of doing that at the moment) and with that I can resend it with updated

Re: [PATCH v5 1/4] leds: core: add generic support for RGB Color LED's

Hi! > >>The "color" attribute would contain "R G B" values. Setting the "color" > >>attribute of any of the three LED class devices would affect brightness > >>properties (i.e. constituent colors) of the remaining two ones. > >>It would result in disabling any active triggers and writing all the

Re: [PATCH v10 3/9] dt-bindings: phy: tegra-xusb-padctl: Add Tegra210 support

On 04/06/2016 11:08 AM, Thierry Reding wrote: On Tue, Apr 05, 2016 at 03:10:16PM -0600, Stephen Warren wrote: On 04/05/2016 08:44 AM, Thierry Reding wrote: On Wed, Mar 16, 2016 at 11:59:44AM -0600, Stephen Warren wrote: On 03/04/2016 09:19 AM, Thierry Reding wrote: From: Thierry Reding

Re: [RFT PATCH 0/4] usb: dwc2: Fix core reset and force mode delay problems

Am 07.04.2016 um 20:41 schrieb John Youn : > On 3/31/2016 2:44 PM, Michael Niewoehner wrote: >> Hi John, >> >> Am 29.03.2016 um 04:36 schrieb John Youn : >> >>> Hi, >>> >>> The following patch series addresses the core reset and force mode >>>

Re: [Linux-v4.6-rc2] atkbd serio0: Unknown key pressed (translated set 2, code 0xa8 on isa0060/serio0).

On Wed, 6 Apr 2016, Dmitry Torokhov wrote: > > I forgot to tell that I have some patches on top of vanilla Linux v4.6-rc2. > > > > Dropping the patches from makes > > the issue go away. > > Unsure what is the cause. > > Hmm, this is quite curious, none of the recent patches in >

Re: [RFT PATCH 0/4] usb: dwc2: Fix core reset and force mode delay problems

On 3/31/2016 2:44 PM, Michael Niewoehner wrote: > Hi John, > > Am 29.03.2016 um 04:36 schrieb John Youn : > >> Hi, >> >> The following patch series addresses the core reset and force mode >> delay problems we have been seeing on dwc2 for some platforms. >> >> I think I

Re: [PATCH] usb: core: hub: hub_port_init lock controller instead of bus

On Wed, Feb 10, 2016 at 07:13:38PM +0200, Mathias Nyman wrote: > > Most likely xhci is messed up after two device slots are in default state at > the same time. > This happens when both threads are in hub_port_init() have called > hub_port_reset() > > The issue becomes visible when the the

Re: [PATCH v2 0/6] usb: xhci: plat: get rid of xhci_plat_type_is()

Hi Felipe, On mar., mars 29 2016, Felipe Balbi wrote: > This 6-patch series gets rid of the pointless > xhci_plat_type_is() in favour of a nicer setup where > we initialize function pointers ahead of time using > driver_data. That way we help the code look a

Re: [PATCH] usb: f_mass_storage: test whether thread is running before starting another

> On Thu, 7 Apr 2016, Michal Nazarewicz wrote: >> This makes me suspect it’s not possible to link a function instance to >> the same configuration twice, but now that I think about it, I’m not >> quite sure what would happen if one did: >> >> ln -s functions/mass_storage.0 configs/c.1/foo >>

Re: [PATCH] phy: bcm-ns-usb2: new driver for USB 2.0 PHY on Northstar

On 04/05/2016 09:34 PM, Jon Mason wrote: > > > On Wed, Mar 30, 2016 at 5:32 PM, Jon Mason > wrote: > > On Tue, Mar 29, 2016 at 10:01 AM, Rafał Miłecki > wrote: > > Northstar is

Re: [PATCH v3 00/16] da8xx USB clocks

On 03/24/2016 06:51 PM, David Lechner wrote: This is a reworking of the v2 series based of feedback and review. There were very many suggestions, so hopefully I didn't miss any. Here are the highlights... New stuff: * Fixed the davinci device tree declarations to use the preferred DT address

Re: raid 5 creation fails on usb3 connected drives kernel 4.4.x, 4.5

On Fri, Apr 08, 2016 at 01:34:51AM +1000, Brian Chadwick wrote: > On 08/04/16 00:44, Greg KH wrote: > > On Thu, Apr 07, 2016 at 03:04:55PM +1000, Brian Chadwick wrote: > > > On 06/04/16 19:53, Greg KH wrote: > > > > On Tue, Apr 05, 2016 at 06:42:51PM +1000, Brian Chadwick wrote: > > > > > SETUP: >

[PATCH] usb: wusbcore: remove unreachable code

The call to wusb_dev_sysfs_rm() which is just after return will never be executed. On checking the code, wusb_dev_sysfs_add() is the last one to be executed so even if that fails we do not need wusb_dev_sysfs_rm() in the error path. Signed-off-by: Sudip Mukherjee

Re: raid 5 creation fails on usb3 connected drives kernel 4.4.x, 4.5

On 08/04/16 00:44, Greg KH wrote: On Thu, Apr 07, 2016 at 03:04:55PM +1000, Brian Chadwick wrote: On 06/04/16 19:53, Greg KH wrote: On Tue, Apr 05, 2016 at 06:42:51PM +1000, Brian Chadwick wrote: SETUP: i7 16GB Computer. 1 x PCI-x USB3 adaptor card (i think uses xhci-hcd)04:00.0 USB

Re: [GIT PULL] usb: fixes for v4.6-rc3

On Thu, Apr 07, 2016 at 01:39:23PM +0300, Felipe Balbi wrote: > > Hi Greg, > > here's my second pull request for this -rc cycle. Patches have been > tested (where applicable) on 3 different Intel platforms (including the > one for which we're adding a new PCI ID - Broxton). > > Let me know if

Re: Oops in 4.6-rc2: NULL pointer dereference in cdc-acm

On Thu, Apr 07, 2016 at 08:59:38AM +0200, Oliver Neukum wrote: > On Wed, 2016-04-06 at 22:48 +0200, Gabriele Mazzotta wrote: > > Hi, > > > > I'm getting a kernel oops when I plug some smartphone via USB to my > > laptop, which is currently running the v4.6-rc2. > > > > The problem seems to be

Re: [PATCH] usb: f_mass_storage: test whether thread is running before starting another

Hi, On 7.04.2016 17:25, Alan Stern wrote: On Thu, 7 Apr 2016, Michal Nazarewicz wrote: Sounds good to me. I’d love someone to test this patch (I sadly have no way of doing that at the moment) and with that I can resend it with updated message. Ivaylo should be able to try it. I

Re: raid 5 creation fails on usb3 connected drives kernel 4.4.x, 4.5

On Thu, Apr 07, 2016 at 03:04:55PM +1000, Brian Chadwick wrote: > On 06/04/16 19:53, Greg KH wrote: > > On Tue, Apr 05, 2016 at 06:42:51PM +1000, Brian Chadwick wrote: > > > SETUP: > > > > > > i7 16GB Computer. > > > > > > 1 x PCI-x USB3 adaptor card (i think uses xhci-hcd)04:00.0 USB

Re: [PATCHv2 / RESEND 1/2] usb: storage: scsiglue: further describe our 240 sector limit

On Thu, 7 Apr 2016, Felipe Balbi wrote: > Just so we have some sort of documentation as to why > we limit our Mass Storage transfers to 240 sectors, > let's update the comment to make clearer that > devices were found that would choke with larger > transfers. > > While at that, also make sure to

Re: [PATCHv2 / RESEND 2/2] usb: storage: scsiglue: limit USB3 devices to 2048 sectors

On Thu, 7 Apr 2016, Felipe Balbi wrote: > USB3 devices, because they are much newer, have much > less chance of having issues with larger transfers. > > We still keep a limit because anything above 2048 > sectors really rendered negligible speed > improvements, so we will simply ignore > that.

Re: [PATCH] usb: f_mass_storage: test whether thread is running before starting another

On Thu, 7 Apr 2016, Michal Nazarewicz wrote: > Sounds good to me. I’d love someone to test this patch (I sadly have no > way of doing that at the moment) and with that I can resend it with > updated message. Ivaylo should be able to try it. > > BTW, is configfs capable of adding a single

Re: [PATCH 3/7] xhci: Don't suspend a xhci usb bus if there is a pending event.

On Thu, 7 Apr 2016, Mathias Nyman wrote: > > In this case there may be alternatives. For example, you could just > > delay a few ms until the pending event has been handled. Or, if you > > really just want to prevent runtime suspend, you should check to see if > > this was a runtime suspend and

Re: [PATCH v1 1/2] dt/bindings/usb: Add bindings for PIC32 MUSB driver.

On 4/7/2016 4:24 PM, Purna Chandra Mandal wrote: Document devicetree binding for the USB controller Device tree. ack. and USB Phy found on Microchip PIC32 class devices. PHY. ack. Signed-off-by: Purna Chandra Mandal ---

Re: [PATCH v2 1/2] dt/bindings/usb: Add bindings for PIC32 MUSB driver.

On 04/07/2016 07:04 PM, Sergei Shtylyov wrote: > On 4/7/2016 3:32 PM, Purna Chandra Mandal wrote: > >> Document devicetree binding for the USB controller >> and USB Phy found on Microchip PIC32 class devices. >> >> Signed-off-by: Purna Chandra Mandal >> >> --- >> >>

Re: [PATCH v2 1/2] dt/bindings/usb: Add bindings for PIC32 MUSB driver.

On 4/7/2016 3:32 PM, Purna Chandra Mandal wrote: Document devicetree binding for the USB controller and USB Phy found on Microchip PIC32 class devices. Signed-off-by: Purna Chandra Mandal --- Changes in v2: None .../bindings/usb/microchip,pic32-musb.txt

Re: [PATCH v1 1/2] dt/bindings/usb: Add bindings for PIC32 MUSB driver.

On 04/07/2016 06:42 PM, Sergei Shtylyov wrote: > On 4/7/2016 4:02 PM, Purna Chandra Mandal wrote: > Document devicetree binding for the USB controller >>> >>> Device tree. >>> >> ack. >> and USB Phy found on Microchip PIC32 class devices. >>> >>> PHY. >>> >> ack. >>

Re: [PATCH v1 1/2] dt/bindings/usb: Add bindings for PIC32 MUSB driver.

On 4/7/2016 4:02 PM, Purna Chandra Mandal wrote: Document devicetree binding for the USB controller Device tree. ack. and USB Phy found on Microchip PIC32 class devices. PHY. ack. Signed-off-by: Purna Chandra Mandal ---

Re: [PATCH v1 1/2] dt/bindings/usb: Add bindings for PIC32 MUSB driver.

On 04/07/2016 06:23 PM, Sergei Shtylyov wrote: > Hello. > > On 4/7/2016 2:16 PM, Purna Chandra Mandal wrote: > >> Document devicetree binding for the USB controller > >Device tree. > ack. >> and USB Phy found on Microchip PIC32 class devices. > >PHY. > ack. >> Signed-off-by: Purna

Re: [PATCH v2 2/2] usb: musb: pic32: Add USB DRC driver for PIC32 OTG controller.

On 04/07/2016 06:09 PM, Felipe Balbi wrote: > Purna Chandra Mandal writes: >> From: Cristian Birsan >> >> This driver adds support of PIC32 MUSB OTG controller as >> dual role device. It implements platform specific glue to >> reuse

Re: [PATCH v1 1/2] dt/bindings/usb: Add bindings for PIC32 MUSB driver.

Hello. On 4/7/2016 2:16 PM, Purna Chandra Mandal wrote: Document devicetree binding for the USB controller Device tree. and USB Phy found on Microchip PIC32 class devices. PHY. Signed-off-by: Purna Chandra Mandal ---

Re: [PATCH v2 2/2] usb: musb: pic32: Add USB DRC driver for PIC32 OTG controller.

Purna Chandra Mandal writes: > From: Cristian Birsan > > This driver adds support of PIC32 MUSB OTG controller as > dual role device. It implements platform specific glue to > reuse musb core. > > Signed-off-by: Cristian Birsan

[PATCH v2 2/2] usb: musb: pic32: Add USB DRC driver for PIC32 OTG controller.

From: Cristian Birsan This driver adds support of PIC32 MUSB OTG controller as dual role device. It implements platform specific glue to reuse musb core. Signed-off-by: Cristian Birsan Signed-off-by: Purna Chandra Mandal

[PATCH v2 1/2] dt/bindings/usb: Add bindings for PIC32 MUSB driver.

Document devicetree binding for the USB controller and USB Phy found on Microchip PIC32 class devices. Signed-off-by: Purna Chandra Mandal --- Changes in v2: None .../bindings/usb/microchip,pic32-musb.txt | 67 ++ 1 file changed, 67

Re: [PATCH v1 2/2] usb: musb: pic32: Add USB DRC driver for PIC32 OTG controller.

Hi Cristian, [auto build test ERROR on balbi-usb/next] [also build test ERROR on v4.6-rc2 next-20160407] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Purna-Chandra-Mandal/dt-bindings-usb

[PATCH v10 2/4] gadget: Support for the usb charger framework

For supporting the usb charger, it adds the usb_charger_init() and usb_charger_exit() functions for usb charger initialization and exit. It will report to the usb charger when the gadget state is changed, then the usb charger can do the power things. Signed-off-by: Baolin Wang

[PATCH v10 3/4] gadget: Integrate with the usb gadget supporting for usb charger

When the usb gadget supporting for usb charger is ready, the usb charger can implement the usb_charger_plug_by_gadget() function and usb_charger_exit() function by getting 'struct usb_charger' from 'struct gadget'. Signed-off-by: Baolin Wang ---

[PATCH v10 4/4] power: wm831x_power: Support USB charger current limit management

Integrate with the newly added USB charger interface to limit the current we draw from the USB input based on the input device configuration identified by the USB stack, allowing us to charge more quickly from high current inputs without drawing more current than specified from others.

[PATCH v10 1/4] gadget: Introduce the usb charger framework

This patch introduces the usb charger driver based on usb gadget that makes an enhancement to a power driver. It works well in practice but that requires a system with suitable hardware. The basic conception of the usb charger is that, when one usb charger is added or removed by reporting from

[PATCH v10 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

Currently the Linux kernel does not provide any standard integration of this feature that integrates the USB subsystem with the system power regulation provided by PMICs meaning that either vendors must add this in their kernels or USB gadget devices based on Linux (such as mobile phones) may not

Re: [PATCH v6 07/12] usb: otg: add OTG/dual-role core

Hi, On 07/04/16 11:52, Yoshihiro Shimoda wrote: > Hi, > >> From: Roger Quadros >> Sent: Tuesday, April 05, 2016 11:05 PM >> >> It provides APIs for the following tasks >> >> - Registering an OTG/dual-role capable controller >> - Registering Host and Gadget controllers to OTG core >> - Providing

[PATCHv2 / RESEND 0/2] usb: storage: increase limit to 2048 sectors

Hi, These patches were already sent last october but I guess I completely forgot about them. They still give me considerable throughput improvement for USB3 storage devices. Let me know if anybody still wants any changes on these patches. cheers Felipe Balbi (2): usb: storage: scsiglue:

[PATCHv2 / RESEND 1/2] usb: storage: scsiglue: further describe our 240 sector limit

Just so we have some sort of documentation as to why we limit our Mass Storage transfers to 240 sectors, let's update the comment to make clearer that devices were found that would choke with larger transfers. While at that, also make sure to clarify that other operating systems have similar,

[PATCHv2 / RESEND 2/2] usb: storage: scsiglue: limit USB3 devices to 2048 sectors

USB3 devices, because they are much newer, have much less chance of having issues with larger transfers. We still keep a limit because anything above 2048 sectors really rendered negligible speed improvements, so we will simply ignore that. Transferring 1MiB should already give us pretty good

Re: [PATCH v10 8/9] usb: xhci: Add NVIDIA Tegra XUSB controller driver

On 07.04.2016 14:05, Thierry Reding wrote: On Thu, Apr 07, 2016 at 02:03:45PM +0300, Mathias Nyman wrote: On 04.03.2016 18:19, Thierry Reding wrote: From: Thierry Reding Add support for the on-chip XUSB controller present on Tegra SoCs. This controller, when loaded with

[PATCH v1 2/2] usb: musb: pic32: Add USB DRC driver for PIC32 OTG controller.

From: Cristian Birsan This driver adds support of PIC32 MUSB OTG controller as dual role device. It implements platform specific glue to reuse musb core. Signed-off-by: Cristian Birsan Signed-off-by: Purna Chandra Mandal

[PATCH v1 1/2] dt/bindings/usb: Add bindings for PIC32 MUSB driver.

Document devicetree binding for the USB controller and USB Phy found on Microchip PIC32 class devices. Signed-off-by: Purna Chandra Mandal --- .../bindings/usb/microchip,pic32-musb.txt | 67 ++ 1 file changed, 67 insertions(+) create

Re: [PATCH v10 8/9] usb: xhci: Add NVIDIA Tegra XUSB controller driver

On Thu, Apr 07, 2016 at 02:03:45PM +0300, Mathias Nyman wrote: > On 04.03.2016 18:19, Thierry Reding wrote: > > From: Thierry Reding > > > > Add support for the on-chip XUSB controller present on Tegra SoCs. This > > controller, when loaded with external firmware, exposes an

Re: [PATCH v10 8/9] usb: xhci: Add NVIDIA Tegra XUSB controller driver

On 04.03.2016 18:19, Thierry Reding wrote: From: Thierry Reding Add support for the on-chip XUSB controller present on Tegra SoCs. This controller, when loaded with external firmware, exposes an interface compliant with xHCI. This driver loads the firmware, starts the

[GIT PULL] usb: fixes for v4.6-rc3

Hi Greg, here's my second pull request for this -rc cycle. Patches have been tested (where applicable) on 3 different Intel platforms (including the one for which we're adding a new PCI ID - Broxton). Let me know if you want anything to be changed. cheers The following changes since commit

Re: [PATCH v6 01/12] usb: hcd: Initialize hcd->flags to 0

On 07/04/16 12:42, Peter Chen wrote: > On Wed, Apr 06, 2016 at 09:32:22AM +0300, Roger Quadros wrote: >> On 06/04/16 09:09, Felipe Balbi wrote: >>> >>> Hi, >>> >>> Roger Quadros writes: diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c index 2ca2cef..6b1930d

Re: [PATCH v2] USB: option: add "D-Link DWM-221 B1" device id

On Thu, Apr 07, 2016 at 12:09:17PM +0200, Bjørn Mork wrote: > Thomas reports: > "Windows: > > 00 diagnostics > 01 modem > 02 at-port > 03 nmea > 04 nic > > Linux: > > T: Bus=02 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 4 Spd=480 MxCh= 0 > D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1

[PATCH v2] USB: option: add "D-Link DWM-221 B1" device id

Thomas reports: "Windows: 00 diagnostics 01 modem 02 at-port 03 nmea 04 nic Linux: T: Bus=02 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 4 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=2001 ProdID=7e19 Rev=02.32 S: Manufacturer=Mobile Connect S:

Re: [PATCH v5 2/2] USB: serial: cp210x: Adding GE Healthcare Device ID

On 07/04/16 10:39, Johan Hovold wrote: On Tue, Mar 29, 2016 at 05:47:29PM +0100, Martyn Welch wrote: The CP2105 is used in the GE Healthcare Remote Alarm Box, with the Manufacturer ID of 0x1901 and Product ID of 0x0194. Signed-off-by: Martyn Welch ---

Re: [PATCH] option.c: Support for Gemalto's Cinterion PH8 and AHxx products added

On Thu, Apr 07, 2016 at 09:48:27AM +, Schemmel Hans-Christoph wrote: > This message and any attachments are intended solely for the addressees and > may contain confidential information. Any unauthorized use or disclosure, > either whole or partial, is prohibited. > E-mails are susceptible

Re: [PATCH] usb: f_mass_storage: test whether thread is running before starting another

>> On Tue, Apr 05 2016, Alan Stern wrote: >>> Suppose one usb_function is carrying out an I/O operation while >>> another one in the same config gets a Set-Interface request from the >>> host. > On Wed, 6 Apr 2016, Michal Nazarewicz wrote: >> That cannot happen. A single instance of mass_storage

Re: [PATCH v5 2/2] USB: serial: cp210x: Adding GE Healthcare Device ID

On 07/04/16 10:55, Johan Hovold wrote: On Thu, Apr 07, 2016 at 10:45:10AM +0100, Martyn Welch wrote: On 07/04/16 10:39, Johan Hovold wrote: On Tue, Mar 29, 2016 at 05:47:29PM +0100, Martyn Welch wrote: The CP2105 is used in the GE Healthcare Remote Alarm Box, with the Manufacturer ID of

Re: [PATCH] USB: option: add "D-Link DWM-221 B1" device id

Johan Hovold writes: > On Mon, Mar 28, 2016 at 10:37:35PM +0200, Bjørn Mork wrote: >> Thomas reports: >> "Windows: >> >> 00 diagnostics >> 01 modem >> 02 at-port >> 03 nmea >> 04 nic >> >> Linux: >> >> T: Bus=02 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 4 Spd=480 MxCh= 0 >> D:

Re: [PATCH] usb: gadget: f_fs: Fix EFAULT generation for async read operations

On Wed, Mar 30 2016, Lars-Peter Clausen wrote: > In the current implementation functionfs generates a EFAULT for async read > operations if the read buffer size is larger than the URB data size. Since > a application does not necessarily know how much data the host side is > going to send it

Re: [PATCH] option.c: Support for Gemalto's Cinterion PH8 and AHxx products added

On Wed, Apr 06, 2016 at 03:20:03PM +, Schemmel Hans-Christoph wrote: > Added support for Gemalto's Cinterion PH8 and AHxx products > with 2 RmNet Interfaces and products with 1 RmNet + 1 USB Audio interface. > > The RmNet and USB Audio interfaces are blacklisted because they will be > handled

Re: [PATCH v6 01/12] usb: hcd: Initialize hcd->flags to 0

On Wed, Apr 06, 2016 at 09:32:22AM +0300, Roger Quadros wrote: > On 06/04/16 09:09, Felipe Balbi wrote: > > > > Hi, > > > > Roger Quadros writes: > >> diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c > >> index 2ca2cef..6b1930d 100644 > >> --- a/drivers/usb/core/hcd.c

RE: [PATCH] option.c: Support for Gemalto's Cinterion PH8 and AHxx products added

> -Original Message- > From: Johan Hovold [mailto:jhov...@gmail.com] On Behalf Of Johan Hovold > Sent: Donnerstag, 7. April 2016 11:23 > To: Schemmel Hans-Christoph > Cc: jo...@kernel.org; gre...@linuxfoundation.org; linux-usb@vger.kernel.org > Subject: Re: [PATCH] option.c: Support for

Re: [PATCH v5 2/2] USB: serial: cp210x: Adding GE Healthcare Device ID

On 07/04/16 10:39, Johan Hovold wrote: On Tue, Mar 29, 2016 at 05:47:29PM +0100, Martyn Welch wrote: The CP2105 is used in the GE Healthcare Remote Alarm Box, with the Manufacturer ID of 0x1901 and Product ID of 0x0194. Signed-off-by: Martyn Welch ---

Re: [PATCH v5 2/2] USB: serial: cp210x: Adding GE Healthcare Device ID

On Tue, Mar 29, 2016 at 05:47:29PM +0100, Martyn Welch wrote: > The CP2105 is used in the GE Healthcare Remote Alarm Box, with the > Manufacturer ID of 0x1901 and Product ID of 0x0194. > > Signed-off-by: Martyn Welch > --- > drivers/usb/serial/cp210x.c | 1 + > 1

Re: [PATCH] USB: option: add "D-Link DWM-221 B1" device id

On Mon, Mar 28, 2016 at 10:37:35PM +0200, Bjørn Mork wrote: > Thomas reports: > "Windows: > > 00 diagnostics > 01 modem > 02 at-port > 03 nmea > 04 nic > > Linux: > > T: Bus=02 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 4 Spd=480 MxCh= 0 > D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1

Re: [PATCH v10 4/9] phy: Add Tegra XUSB pad controller support

Hi, On Wednesday 06 April 2016 10:56 PM, Thierry Reding wrote: > On Wed, Apr 06, 2016 at 06:13:42PM +0530, Kishon Vijay Abraham I wrote: >> On Friday 04 March 2016 09:49 PM, Thierry Reding wrote: > [...] >>> +struct tegra124_xusb_fuse_calibration { >>> + u32 hs_curr_level[3]; >>> + u32

Re: [PATCH] option.c: Support for Gemalto's Cinterion PH8 and AHxx products added

On Wed, Apr 06, 2016 at 03:20:03PM +, Schemmel Hans-Christoph wrote: > Added support for Gemalto's Cinterion PH8 and AHxx products > with 2 RmNet Interfaces and products with 1 RmNet + 1 USB Audio interface. > > The RmNet and USB Audio interfaces are blacklisted because they will be > handled

Re: [PATCH] USB: serial: ftdi_sio: Add support for ICP DAS I-756xU devices

On Wed, Mar 16, 2016 at 12:11:35PM -0400, Johan Hovold wrote: > On Wed, Mar 16, 2016 at 11:55:49AM -0400, Josh Boyer wrote: > > On Thu, Mar 10, 2016 at 9:48 AM, Josh Boyer > > wrote: > > > A Fedora user reports that the ftdi_sio driver works properly for the > > > ICP

RE: [PATCH v6 07/12] usb: otg: add OTG/dual-role core

Hi, > From: Roger Quadros > Sent: Tuesday, April 05, 2016 11:05 PM > > It provides APIs for the following tasks > > - Registering an OTG/dual-role capable controller > - Registering Host and Gadget controllers to OTG core > - Providing inputs to and kicking the OTG state machine > > Provide a

Re: [PATCH 3/7] xhci: Don't suspend a xhci usb bus if there is a pending event.

On 07.04.2016 00:25, Alan Stern wrote: On Wed, 6 Apr 2016, Greg KH wrote: On Wed, Apr 06, 2016 at 04:08:04PM +0300, Mathias Nyman wrote: We don't want to runtime suspend a bus if there is an event pending. The roothub on a NEC uPD720200 host with a single USB3 device connected might go back

Re: driver migration

Hello Kind of Driver: Driver for a dongle usb-> serial Manufacturer: Io-Data Device: USB-RSA (based on EZUSB-CHip) Reference: My last post from 2016-04-02 19:49:40 GMT Description: The blocking behaviour that I reported in my last post seems to be induced by the set_bit and submit_urb in

Re: Oops in 4.6-rc2: NULL pointer dereference in cdc-acm

On Wed, 2016-04-06 at 22:48 +0200, Gabriele Mazzotta wrote: > Hi, > > I'm getting a kernel oops when I plug some smartphone via USB to my > laptop, which is currently running the v4.6-rc2. > > The problem seems to be caused by a81cf9799ad7 ("cdc-acm: implement > put_char() and flush_chars()"). >

Re: [PATCH 1/2] usb: dwc2: Add reset control to dwc2

On 3/28/2016 10:38 PM, dingu...@opensource.altera.com wrote: > From: Dinh Nguyen > > Allow for platforms that have a reset controller driver in place to bring > the USB IP out of reset. > > Signed-off-by: Dinh Nguyen > Cc: John

Re: [PATCH v9 1/4] gadget: Introduce the usb charger framework

On 7 April 2016 at 12:56, Felipe Balbi wrote: > > Hi, > > Peter Chen writes: >> On Wed, Apr 06, 2016 at 01:25:06PM +0300, Felipe Balbi wrote: >>> >>> Hi, >>> >>> Peter Chen writes: >>> > On Wed, Apr 06, 2016 at 11:05:26AM +0300,