Re: autodetect USB MTP device characteristics without libusb_open()

Linus Walleij wrote: > > Windows requests the 0xee string descriptor from *every* device, > > unless the same vid and pid has been seen before on the system. > > I had no clue about that... have you seen this from USB traces? I didn't look at traces, but Microsoft documents it, and testing shows

Re: autodetect USB MTP device characteristics without libusb_open()

On Tue, Nov 20, 2012 at 7:26 PM, Peter Stuge wrote: > Windows requests the 0xee string descriptor from *every* device, > unless the same vid and pid has been seen before on the system. I had no clue about that... have you seen this from USB traces? I have seen devices crash when 0xee is request

Re: Cannot open two tyyACMs at a time when using 2514b USB hub

Hi Oliver, thank you for answer. A trace with usbmon as described in Documentation/usb should show what IO goes wrong. Trace is attached bellow. It was created with following sequence 1. attach USB modem (driver is loaded, ttyACMs created by udev) 2. cat /dev/ttyACM0 & (works fine) 3 cat /d

Re: [PATCH] ezusb: add dependency to USB

- Ursprüngliche Mail - > On Thu, Nov 22, 2012 at 07:10:50PM +0100, Rene Buergel wrote: > > This fixes an error during modpost, when ezusb is built into the > > kernel while USB is built as module. > thanks for the fix, I'll queue it up for 3.8 > and > backport it for 3.7-stable as well. >

[PATCH 23/27] arm: mmp: add extern chip support for brownstone

From: Chao Xie Change the board support for usb as extern chip is supported in marvell usb PHY driver Signed-off-by: Chao Xie --- arch/arm/mach-mmp/brownstone.c |2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/arch/arm/mach-mmp/brownstone.c b/arch/arm/mach-mmp/brownsto

[PATCH 24/27] arm: mmp: add extern chip support for ttc_dkb

From: Chao Xie Change the board support for usb as extern chip is supported in marvell usb PHY driver. Signed-off-by: Chao Xie --- arch/arm/mach-mmp/ttc_dkb.c |2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/arch/arm/mach-mmp/ttc_dkb.c b/arch/arm/mach-mmp/ttc_dkb.c ind

[PATCH 26/27] usb: otg: mv_otg: add device tree support

From: Chao Xie All blocks are removed. Add the device tree support for otg. Signed-off-by: Chao Xie --- drivers/usb/otg/mv_otg.c | 127 + drivers/usb/otg/mv_otg.h |6 +- 2 files changed, 107 insertions(+), 26 deletions(-) diff --git a/drivers/u

[PATCH 27/27] usb: ehci: ehci-mv: add device tree support

From: Chao Xie All blocks are removed. Add the device tree support for ehci. Signed-off-by: Chao Xie --- drivers/usb/host/ehci-mv.c | 104 +--- 1 files changed, 79 insertions(+), 25 deletions(-) diff --git a/drivers/usb/host/ehci-mv.c b/drivers/usb/hos

[PATCH 22/27] usb: otg: mv_otg: add extern chip support

From: Chao Xie It does the similar things as what we do for udc driver. Signed-off-by: Chao Xie --- drivers/usb/otg/mv_otg.c | 63 - drivers/usb/otg/mv_otg.h |3 ++ 2 files changed, 31 insertions(+), 35 deletions(-) diff --git a/drivers/usb/ot

[PATCH 25/27] usb: gadget: mv_udc: add device tree support

From: Chao Xie In original driver, we have callbacks in platform data, and some dynamically allocations variables in platform data. Now, these blocks are removed, the device tree support is easier now. Signed-off-by: Chao Xie --- drivers/usb/gadget/mv_udc.h |5 +- drivers/usb/gadget/m

[PATCH 18/27] arm: mmp: remove usb devices from pxa168

From: Chao Xie Signed-off-by: Chao Xie --- arch/arm/mach-mmp/pxa168.c | 42 -- 1 files changed, 0 insertions(+), 42 deletions(-) diff --git a/arch/arm/mach-mmp/pxa168.c b/arch/arm/mach-mmp/pxa168.c index b7f074f..dd3a68b 100644 --- a/arch/arm/mach-mmp/

[PATCH 19/27] usb: phy: mv_usb2_phy: add externel chip support

From: Chao Xie For the vbus and idpin detection. It may be completed by some external chip, for example the pmic chip 88pm860x in driver/mfd can do it. Although the usb controller can detect the vbus and id pin, but it need clock on and PHY enabled to detect the vbus/idpin. It will increase the p

[PATCH 21/27] usb: ehci: ehci-mv: add extern chip support

From: Chao Xie It does the similar things as what we do for udc driver. Signed-off-by: Chao Xie --- drivers/usb/host/ehci-mv.c | 12 ++-- 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/usb/host/ehci-mv.c b/drivers/usb/host/ehci-mv.c index be504fd..171e145 1006

[PATCH 16/27] arm: ttc_dkb: add usb support

From: Chao Xie for ttc_dkb board, add udc/otg/ehci support Signed-off-by: Chao Xie --- arch/arm/mach-mmp/ttc_dkb.c | 30 +++--- 1 files changed, 19 insertions(+), 11 deletions(-) diff --git a/arch/arm/mach-mmp/ttc_dkb.c b/arch/arm/mach-mmp/ttc_dkb.c index ce55fd8..09

[PATCH 20/27] usb: gadget: mv_udc: add extern chip support

From: Chao Xie Because arch-mmp will make use of irq domain for irq allocation, the irqs allocated for PMIC is dynamical. The vbus/idpin irqs from PMIC can not be passed by platform data. Using the extern chip APIs provides by PHY driver can solve this problem. Marvell usb PHY driver provides a m

[PATCH 17/27] arm: mmp: remove the usb phy setting

From: Chao Xie phy setting are formatted into a phy driver at drivers/usb/phy, we do not need do the setting in SOC files. Signed-off-by: Chao Xie --- arch/arm/mach-mmp/devices.c | 278 - arch/arm/mach-mmp/include/mach/regs-usb.h | 253 --

[PATCH 11/27] usb: ehci: ehci-mv: use PHY driver for ehci

From: Chao Xie Originaly, ehci driver will call the callbacks in platform data for PHY initialization and shut down. With PHY driver, it will call the APIs provided by PHY driver for PHY initialization and shut down. It removes the callbacks in platform data, and at same time it removes one block

[PATCH 15/27] arm: brownstone: add usb support for the board

From: Chao Xie for brownstone board, add the udc/otg/ehci support Signed-off-by: Chao Xie --- arch/arm/mach-mmp/brownstone.c | 47 1 files changed, 47 insertions(+), 0 deletions(-) diff --git a/arch/arm/mach-mmp/brownstone.c b/arch/arm/mach-mmp/brown

[PATCH 14/27] arm: pxa910: change the defintion of usb devices

From: Chao Xie because phy is seperated from the usb controller driver, we can use the common pxa_device_desc for device register. Signed-off-by: Chao Xie --- arch/arm/mach-mmp/include/mach/pxa910.h |7 --- arch/arm/mach-mmp/pxa910.c |4 2 files changed, 8 inserti

[PATCH 12/27] usb: otg: mv_otg: use PHY driver for otg

From: Chao Xie Originaly, otg driver will call the callbacks in platform data for PHY initialization and shut down. With PHY driver, it will call the APIs provided by PHY driver for PHY initialization and shut down. It removes the callbacks in platform data, and at same time it removes one block

[PATCH 13/27] arm: mmp2: change the defintion of usb devices

From: Chao Xie add the udc/otg/ehci devices for mmp2 Signed-off-by: Chao Xie --- arch/arm/mach-mmp/include/mach/mmp2.h |4 arch/arm/mach-mmp/mmp2.c |4 2 files changed, 8 insertions(+), 0 deletions(-) diff --git a/arch/arm/mach-mmp/include/mach/mmp2.h b/arch/ar

[PATCH 09/27] usb: phy: mv_usb2: add PHY driver for marvell usb2 controller

From: Chao Xie The PHY is seperated from usb controller. The usb controller used in marvell pxa168/pxa910/mmp2 are same, but PHY initialization may be different. the usb controller can support udc/otg/ehci, and for each of the mode, it need PHY to initialized before use the controller. Directly w

[PATCH 10/27] usb: gadget: mv_udc: use PHY driver for udc

From: Chao Xie Originaly, udc driver will call the callbacks in platform data for PHY initialization and shut down. With PHY driver, it will call the APIs provided by PHY driver for PHY initialization and shut down. It removes the callbacks in platform data, and at same time it removes one block

[PATCH 08/27] usb: gadget: mv_udc: fix the value of tranceiver

From: Chao Xie usally we will use udc->tranceiver == NULL or udc->tranceiver != NULL. So when failed to get the udc->tranceiver by usb_get_phy(), we directly set udc->tranceiver to be NULL. Then the source code will not need macro IS_ERR_OR_NULL() for udc->tranceiver judgement. It can reduce the

[PATCH 06/27] usb: host: ehci-mv: fix clk APIs

From: Chao Xie the clock common driver changes, and arch-mmp will make use of the common clock driver instead of its own. So for enable clock. first prepare the clock then enable the clock. for disable clock first disable the clock then unprepare the clock Signed-off-by: Chao Xie --- drivers/

[PATCH 07/27] usb: host: ehci-mv: remove unused variable

From: Chao Xie Signed-off-by: Chao Xie --- drivers/usb/host/ehci-mv.c |1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/usb/host/ehci-mv.c b/drivers/usb/host/ehci-mv.c index 6c56297..3065809 100644 --- a/drivers/usb/host/ehci-mv.c +++ b/drivers/usb/host/ehci-mv.c

[PATCH 04/27] usb: otg: mv_otg: use devm_xxx for probe

From: Chao Xie use devm_xxx for otg driver probe. So we do need care about the resources release in driver remove or failure handling in driver probe. Signed-off-by: Chao Xie --- drivers/usb/otg/mv_otg.c | 82 - 1 files changed, 22 insertions(+), 6

[PATCH 05/27] usb: otg: mv_otg: fix the clk APIs

From: Chao Xie the clock common driver changes, and arch-mmp will make use of the common clock driver instead of its own. So for enable clock. first prepare the clock then enable the clock. for disable clock first disable the clock then unprepare the clock Signed-off-by: Chao Xie --- drivers/

[PATCH 03/27] usb: gadget: mv_udc: fix the clk APIs

From: Chao Xie the clock common driver changes, and arch-mmp will make use of the common clock driver instead of its own. So for enable clock. first prepare the clock then enable the clock. for disable clock first disable the clock then unprepare the clock Signed-off-by: Chao Xie --- drivers/

[PATCH 02/27] usb: gadget: mv_udc: use devm_xxx for probe

From: Chao Xie use devm_xxx for udc driver probe. So we do need care about the resources release in driver remove or failure handling in driver probe. Signed-off-by: Chao Xie --- drivers/usb/gadget/mv_udc_core.c | 156 ++ 1 files changed, 56 insertions(+),

[PATCH 01/27] usb: gadget: mv_udc: use udc_start and udc_stop functions

From: Chao Xie This patches converts the driver into the new style start/stop interface. As a result the driver no longer uses the static global the_conroller variable. Signed-off-by: Chao Xie --- drivers/usb/gadget/mv_udc_core.c | 81 +- 1 files changed,

[PATCH 00/27] mv-usb fix and enhancement patches

From: Chao Xie The patches are divied into 3 parts 1. bug fixes usb: gadget: mv_udc: use udc_start and udc_stop functions usb: gadget: mv_udc: use devm_xxx for probe usb: gadget: mv_udc: fix the clk APIs usb: otg: mv_otg: use devm_xxx for probe usb: otg: mv_otg: fix the clk APIs usb:

Re: [alsa-devel] [PATCH] usb: add USB_QUIRK_RESET_RESUME for M-Audio 49

Jonathan Nieder wrote: > Some USB MIDI keyboards fail to operate after a USB autosuspend. Make that *all* USB MIDI devices with input ports. This is not a bug in the device, but one of the many bugs introduced with the autosuspend code in . That patch do

[PATCH] usb: add USB_QUIRK_RESET_RESUME for M-Audio 49

Some USB MIDI keyboards fail to operate after a USB autosuspend. The device is recognized by ALSA, but no events are received and the device goes quiet. $ amidi -l Dir DeviceName IO hw:1,0,0 Oxygen 49 MIDI 1 $ amidi -p hw:1,0,0 -d <... play some notes

Re: [PATCH] smsc: Add logging message newlines

From: Joe Perches Date: Sat, 24 Nov 2012 03:27:49 -0800 > Avoid any possible message logging interleaving by adding > missing newlines. > > Align arguments. > > Signed-off-by: Joe Perches Applied. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message

[PATCH] USB: option: blacklist network interface on Huawei E173

The Huawei E173 will normally appear as 12d1:1436 in Linux. But the modem has another mode with different device ID and a slightly different set of descriptors. This is the mode used by Windows like this: 3Modem: USB\VID_12D1&PID_140C&MI_00\6&3A1D2012&0& Networkcard: USB\VID_12D1&PID

[PATCH] net: qmi_wwan: add Huawei E173

The Huawei E173 is a QMI/wwan device which normally appear as 12d1:1436 in Linux. The descriptors displayed in that mode will be picked up by cdc_ether. But the modem has another mode with a different device ID and a slightly different set of descriptors. This is the mode used by Windows like this

Re: kmemleak report on isp1763 and sierra MC8705

On Tue, 2012-11-20 at 17:15 -0800, Greg Kroah-Hartman wrote: > On Wed, Nov 14, 2012 at 06:52:18PM +0100, Johan Hovold wrote: > > On Wed, Nov 14, 2012 at 12:12:01PM -0500, Richard Retanubun wrote: > > > On 10/11/12 09:30 AM, Johan Hovold wrote: > > > Hi Johan, > > > > > > > There was a reference-co

Re: [PATCH v3 5/7] usb: chipidea: usbmisc: add support for ahb, ipg and per clock

On Fri, Nov 23, 2012 at 05:20:51PM +0100, Michael Grzeschik wrote: > > usbphy: used to transfer data > > (like your per) > > The "per" clk is a different clk than the usbphy. We have an usbphy clk > aswell on the mx5x. As discussed before [1], we need a solution to enable > the usbphy clk. The cur

Re: [PATCH v3 6/7] usb: chipidea: usbmisc: add mx53 support

On Fri, Nov 23, 2012 at 11:02:13AM +0100, Marc Kleine-Budde wrote: > On 11/23/2012 07:53 AM, Peter Chen wrote: > > On Wed, Nov 21, 2012 at 03:06:32PM +0100, Michael Grzeschik wrote: > >> This adds mx53 as the next user of the usbmisc driver and makes it > >> possible to disable the overcurrent-dete

Re: [PATCH v3 6/7] usb: chipidea: usbmisc: add mx53 support

On Fri, Nov 23, 2012 at 08:39:39AM +0100, Sascha Hauer wrote: > On Fri, Nov 23, 2012 at 02:53:41PM +0800, Peter Chen wrote: > > On Wed, Nov 21, 2012 at 03:06:32PM +0100, Michael Grzeschik wrote: > > > This adds mx53 as the next user of the usbmisc driver and makes it > > > possible to disable the o