gmane.linux.usb.general

FROM MRS SUSAN SHABANGU(OPEN THE ATTACH FILES)

FROM MRS SUSAN SHABANGU — 2012-05-26T10:56:23

[PATCH] USB: ftdi-sio: Add support for RT Systems USB-RTS01 serial adapter

Evan McNabb — 2012-05-26T02:46:14

Add support for RT Systems USB-RTS01 USB to Serial adapter:
http://www.rtsystemsinc.com/Photos/USBRTS01.html

Tested by controlling Icom IC-718 amateur radio transceiver via hamlib.

Signed-off-by: Evan McNabb <evan-2BOxfIlzoBpAfugRpC6u6w< at >public.gmane.org>

diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
index 8c084ea..bc912e5 100644
--- a/drivers/usb/serial/ftdi_sio.c
+++ b/drivers/usb/serial/ftdi_sio.c
< at >< at > -737,6 +737,7 < at >< at > static struct usb_device_id id_table_combined [] = {
 { USB_DEVICE(TELLDUS_VID, TELLDUS_TELLSTICK_PID) },
 { USB_DEVICE(RTSYSTEMS_VID, RTSYSTEMS_SERIAL_VX7_PID) },
 { USB_DEVICE(RTSYSTEMS_VID, RTSYSTEMS_CT29B_PID) },
+{ USB_DEVICE(RTSYSTEMS_VID, RTSYSTEMS_RTS01_PID) },
 { USB_DEVICE(FTDI_VID, FTDI_MAXSTREAM_PID) },
 { USB_DEVICE(FTDI_VID, FTDI_PHI_FISCO_PID) },
 { USB_DEVICE(TML_VID, TML_USB_SERIAL_PID) },
diff --git a/drivers/usb/serial/ftdi_sio_ids.h b/drivers/usb/serial/ftdi_sio_ids.h
index f3c7c78..5661c7e 100644
--- a/drivers/usb/serial/ftdi_sio_ids.

looking for kickstart advice for CP2112, usb-i2c bridge

Jean-François Dagenais — 2012-05-26T00:52:33

Hi all,

FYI, I'm a participating kernel device driver developer (i2c, w1, uio) but a 
complete USB noob.

I want to make a proper in-kernel i2c master driver for the Silabs CP2112 usb 
to smbus bridge (actually i2c compliant). The device is presented as HID and 
uses reports for operation. (see 
http://www.silabs.com/Support%20Documents/TechnicalDocs/AN495.pdf )

Silabs expects it's customers to drive the chip from userspace using hiddev in 
the kernel. This prevents users from harnessing all of the i2c client drivers 
in the kernel, hence this effort. (unless I am missing something?)

I have my CP2112 eval kit with me and I'm ready to get started but I'd like 
some pointers to get on the right track ASAP.

- as per device driver customs, which existing driver (patch or already merged) 
  should be used as template?
- where does such a driver belong? I'm guessing drivers/i2c/busses/i2c-cp2112.c
- would I use the same internal APIs that the IOCTLs of hiddev use for example?
- what else should I read/look-at/

(unknown)

robothroli company — 2012-05-25T13:45:54

 i am robothroli, Purchase manager from roli Merchant Ltd. We are
Import/export Company based in taiwan. We are interested in purchasing
your product and I would like to make an inquiry. Please inform me on:

Sample availability and price
Minimum order quantity
FOB Prices

Sincerely
Purchase Manager
robothroli



--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] usb: musb_gadget: fix crash caused by dangling pointer

Grazvydas Ignotas — 2012-05-25T21:21:33

usb_ep_ops.disable must clear external copy of the endpoint descriptor,
otherwise musb crashes after loading/unloading several gadget modules
in a row:

Unable to handle kernel paging request at virtual address bf013730
pgd = c0004000
[bf013730] *pgd=8f26d811, *pte=00000000, *ppte=00000000
Internal error: Oops: 7 [#1]
Modules linked in: g_cdc [last unloaded: g_file_storage]
CPU: 0    Not tainted  (3.2.17 #647)
PC is at musb_gadget_enable+0x4c/0x24c
LR is at _raw_spin_lock_irqsave+0x4c/0x58
[<c027c030>] (musb_gadget_enable+0x4c/0x24c) from [<bf01b760>] (gether_connect+0x3c/0x19c [g_cdc])
[<bf01b760>] (gether_connect+0x3c/0x19c [g_cdc]) from [<bf01ba1c>] (ecm_set_alt+0x15c/0x180 [g_cdc])
[<bf01ba1c>] (ecm_set_alt+0x15c/0x180 [g_cdc]) from [<bf01ecd4>] (composite_setup+0x85c/0xac4 [g_cdc])
[<bf01ecd4>] (composite_setup+0x85c/0xac4 [g_cdc]) from [<c027b744>] (musb_g_ep0_irq+0x844/0x924)
[<c027b744>] (musb_g_ep0_irq+0x844/0x924) from [<c027a97c>] (musb_interrupt+0x79c/0x864)
[<c027a97c>] (musb_interrupt+0x79c/0x8

[PATCH V4] USB: DWC3: Fix missed isoc IN transaction

Pratyush Anand — 2012-05-25T13:24:56

If an IN transfer is missed on isoc endpoint, then driver must insure
that next ep_queue is properly handled.
This patch fixes this issue by starting a new transfer for next queued
request.

Signed-off-by: Pratyush Anand <pratyush.anand-qxv4g6HH51o< at >public.gmane.org>
Signed-off-by: Felip Balbi <balbi-l0cyMroinI0< at >public.gmane.org>
---
 drivers/usb/dwc3/core.h   |    3 ++
 drivers/usb/dwc3/gadget.c |   73 ++++++++++++++++++++++++++++++---------------
 2 files changed, 52 insertions(+), 24 deletions(-)

diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
index c51cece..1210dae 100644
--- a/drivers/usb/dwc3/core.h
+++ b/drivers/usb/dwc3/core.h
< at >< at > -352,6 +352,7 < at >< at > struct dwc3_event_buffer {
  * < at >number: endpoint number (1 - 15)
  * < at >type: set to bmAttributes & USB_ENDPOINT_XFERTYPE_MASK
  * < at >res_trans_idx: Resource transfer index
+ * < at >current_uf: Current uf received through last event parameter
  * < at >interval: the intervall on which the ISOC transfer is started
  * < at >name: a human readable name e.g. ep1ou

[PATCH V3] USB: DWC3: Fix missed isoc IN transaction

Pratyush Anand — 2012-05-25T12:48:40

If an IN transfer is missed on isoc endpoint, then driver must insure
that next ep_queue is properly handled.
This patch fixes this issue by starting a new transfer for next queued
request.

Signed-off-by: Pratyush Anand <pratyush.anand-qxv4g6HH51o< at >public.gmane.org>
Signed-off-by: Felip Balbi <balbi-l0cyMroinI0< at >public.gmane.org>
---
 drivers/usb/dwc3/core.h   |    3 ++
 drivers/usb/dwc3/gadget.c |   72 ++++++++++++++++++++++++++++++---------------
 2 files changed, 51 insertions(+), 24 deletions(-)

diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
index c51cece..1210dae 100644
--- a/drivers/usb/dwc3/core.h
+++ b/drivers/usb/dwc3/core.h
< at >< at > -352,6 +352,7 < at >< at > struct dwc3_event_buffer {
  * < at >number: endpoint number (1 - 15)
  * < at >type: set to bmAttributes & USB_ENDPOINT_XFERTYPE_MASK
  * < at >res_trans_idx: Resource transfer index
+ * < at >current_uf: Current uf received through last event parameter
  * < at >interval: the intervall on which the ISOC transfer is started
  * < at >name: a human readable name e.g. ep1ou

Code flow from device connection to device node in /dev creation

prasannatsmkumar — 2012-05-25T06:07:02

Hi,

I have been looking into USB code. I have some basic idea of what is
going on but still I have some doubts which I try to explain here.

I have explained how the code flow takes place as per my understanding,
My current understanding:

1. USB Device connected physically.
2. khubd detects the connection of USB device (I hope that khub gets
interrupt from Host Controller).
3. Kernel notifies the user space about the device connection
(probably udev involves in this).
4. Driver for the corresponding device is detected using the device
VID/PID and loaded (modprobe is loading the driver).
5. A device file (nod in /dev - like /dev/ttyUSB0) is created for the
USB device.

Is my understanding correct?

Doubts and Questions:
1. How kernel notifies the user space about the device arrival? What
is the work of udev here?
2. How the device file gets associated with the driver (or device)?
i.e., When a user space code does a open or write call to the device
file (e.g., /dev/ttyUSB0) who determines the correct driver

Why USB LPM is not supported on non-root hub?

prasannatsmkumar — 2012-05-25T05:54:11

Hi,

I have been looking into USB stuff. In the EHCI driver code I could
see the comment that "we only support lpm device connected to root hub
yet" in drivers/usb/host/ehci-pci.c line 466 (3.4 kernel -
http://lxr.free-electrons.com/source/drivers/usb/host/ehci-pci.c#L466).
Is there any reason to not support lpm in devices connected to hub
(other than root hub)? Also inside ehci_lpm_check function in
drivers/usb/host/ehci-lpm.c (3.4 kernel -
http://lxr.free-electrons.com/source/drivers/usb/host/ehci-lpm.c) the
USB device is asked to go to LPM mode and there is a wait for 10ms. I
guess the LPM transition (L0 to L1 state transition) should take place
within some micro seconds then why should we wait for 10ms for ACK?

I will greatly appreciate if I could help in someway in solving
technical difficulties (if any).

Thanks and Regards,
Prasanna Kumar T S M
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org
More maj

[PATCH] usb: chipidea: select USB_EHCI_ROOT_HUB_TT in USB_CHIPIDEA_HOST of Kconfig

Richard Zhao — 2012-05-25T02:44:47

ci13xxx host needs Root Hub Transaction Translators.

Reported-by: Shawn Guo <shawn.guo-KZfg59tc24xl57MIdRCFDg< at >public.gmane.org>
Signed-off-by: Richard Zhao <richard.zhao-KZfg59tc24xl57MIdRCFDg< at >public.gmane.org>
---
 drivers/usb/chipidea/Kconfig |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/drivers/usb/chipidea/Kconfig b/drivers/usb/chipidea/Kconfig
index fd36dc8..8337fb5 100644
--- a/drivers/usb/chipidea/Kconfig
+++ b/drivers/usb/chipidea/Kconfig
< at >< at > -20,6 +20,7 < at >< at > config USB_CHIPIDEA_UDC
 
 config USB_CHIPIDEA_HOST
 bool "ChipIdea host controller"
+select USB_EHCI_ROOT_HUB_TT
 help
   Say Y here to enable host controller functionality of the
   ChipIdea driver.

[PATCH v3 00/12] add imx usb driver for mx28/6x

Richard Zhao — 2012-05-25T02:24:13

The work is based on  ci13xxx rework done by Alexander Shishkin.

Status:
  - this version only support host
  - usbotg controler works at host role

Changes since V2:
  - Rebase to Alex's tree
  - Use regulator to control vbus power
  - Remove ARCH check in Kconfig, but add OF_DEV check.
  - Other changes according laster version comments.

Richard Zhao (12):
  usb: otg: add notify_connect/notify_disconnect callback
  usb: chipidea: permit driver bindings pass phy pointer
  usb: ehci-hcd: notify phy when connect change
  usb: otg: add basic mxs phy driver support
  usb: chipidea: add imx platform driver
  ARM: imx6q: correct device name of usbphy and usb controller clock
    export
  ARM: imx6q: add config-on-boot gpios
  ARM: imx6q: add usbphy clocks
  ARM: imx6q: disable usb charger detector
  ARM: dts: imx6q-sabrelite: add usb devices
  ARM: mxs: clk_register_clkdev mx28 usb clocks
  ARM: dts: imx28-evk: add usb devices

 .../devicetree/bindings/arm/config-on-boot.txt     |   12 ++
 .../devicetree/bindin

[PATCH v5] usb: gadget: mv: Add USB 3.0 device driver for Marvell PXA2128 chip.

Yu Xu — 2012-05-25T02:17:47

It supports Marvell USB 3.0 device controller for PXA2128 chip.

Signed-off-by: Yu Xu <yuxu-eYqpPyKDWXRBDgjK7y7TUQ< at >public.gmane.org>
---
 drivers/usb/gadget/Kconfig       |    9 +
 drivers/usb/gadget/Makefile      |    1 +
 drivers/usb/gadget/mv_u3d.h      |  320 ++++++
 drivers/usb/gadget/mv_u3d_core.c | 2074 ++++++++++++++++++++++++++++++++++++++
 4 files changed, 2404 insertions(+)
 create mode 100644 drivers/usb/gadget/mv_u3d.h
 create mode 100644 drivers/usb/gadget/mv_u3d_core.c

diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadget/Kconfig
index 1f93861..4eb92d0 100644
--- a/drivers/usb/gadget/Kconfig
+++ b/drivers/usb/gadget/Kconfig
< at >< at > -316,6 +316,15 < at >< at > config USB_MV_UDC
   USB2.0 OTG controller, which can be configured as high speed or
   full speed USB peripheral.
 
+config USB_MV_U3D
+tristate "MARVELL PXA2128 USB 3.0 controller"
+depends on CPU_MMP3
+select USB_GADGET_DUALSPEED
+select USB_GADGET_SUPERSPEED
+help
+  MARVELL PXA2128 Processor series include a super speed USB3.0 devic

[PATCH v2] usb: musb: davinci: Fix build breakage

Jon Povey — 2012-05-25T01:50:18

This appears to have been broken by
commit 5cfb19ac604a68c030b245561f575c2d1bac1d49
(ARM: davinci: streamline sysmod access)

For now, fix by hardcoding USB_PHY_CTRL and DM355_DEEPSLEEP

Tested on DM365 with defconfig changes.

Signed-off-by: Jon Povey <jon.povey-Ean/AyPsLtfkYMGBc/C6ZA< at >public.gmane.org>
Acked-by: Sekhar Nori <nsekhar-l0cyMroinI0< at >public.gmane.org>
CC: Felipe Balbi <balbi-l0cyMroinI0< at >public.gmane.org>
Cc: <stable-u79uwXL29TY76Z2rM5mHXA< at >public.gmane.org> # v3.4.x
---
Commit message updated after comments. Patch unchanged.

 drivers/usb/musb/davinci.c |    1 +
 drivers/usb/musb/davinci.h |    4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/drivers/usb/musb/davinci.c b/drivers/usb/musb/davinci.c
index 768b4b5..9d63ba4 100644
--- a/drivers/usb/musb/davinci.c
+++ b/drivers/usb/musb/davinci.c
< at >< at > -34,6 +34,7 < at >< at >
 #include <linux/dma-mapping.h>
 
 #include <mach/cputype.h>
+#include <mach/hardware.h>
 
 #include <asm/mach-types.h>
 
diff --git a/drivers/usb/musb/davinci.h b/drive

[PATCH] usb: dwc3: add trace support

Felipe Balbi — 2012-05-24T12:48:24

This patch add a few tracepoints to the DWC3
driver in order to aid debugging.

NYET-Signed-off-by: Felipe Balbi <balbi-l0cyMroinI0< at >public.gmane.org>
---

This is far from ready, but I wanted to see how the
rest of the community feels about adding a few
tracepoints to the dwc3 driver. Any suggestions of
where to add more interesting tracepoints ?

I was thinking of adding a few right before we kick
a transfer which would dump our TRB contents. That's
likely to be useful in most cases.

Any other idea of how to use traces on this driver ?

BTW Gerard/Boyan, this is (in part) what you were
looking for to be able to poke into the running
driver/IP. You could add your own debugging traces
and use them to poke into the device's registers
for your tests, though that's a bit of an abuse of
the interface, I guess ;-)

If all you need, is to print some stuff, we could, instead
use TRACE_EVENT() insteac of DECLARE_TRACE(). It would
become something like:

TRACE_EVENT(dwc3_readl,
TP_PROTO(void __iomem *base, u32 offse

[PATCH 00/15] pending dwc3 patches

Felipe Balbi — 2012-05-24T10:34:35

Hi guys,

here are a few patches I have been holding on a local
branch. Once -rc1 is tagged, I will queue them for v3.6
merge window.

note the Fix for USB30CV's U1/U2 Test provided by Gerard
(thanks dude).

ps: I still have to run a few tests on these patches
myself, so they might still change and you can't find
them on my kernel.org tree yet ;-)

Felipe Balbi (9):
  usb: dwc3: fix a WARN and a comment
  usb: dwc3: handle pending unaligned Control OUT data phase correctly
  usb: dwc3: ep0: switch over to IS_ALIGNED
  usb: dwc3: ep0: align on function signature
  usb: dwc3: ep0: fix a typo in comment
  usb: dwc3: gadget: remove trailing semicolon
  usb: dwc3: drop HAVE_CLK dependency from Exynos glue layer
  usb: dwc3: gadget: prevent DCTL register corruption
  usb: dwc3: gadget: disable U1/U2 on disconnect

Gerard CAUVY (1):
  usb: dwc3: gadget: move AcceptU1Ena and AcceptU2Ena to Reset IRQ

Paul Zimmerman (5):
  usb: dwc3: add definitions for new registers
  usb: dwc3: gadget: reinitialize retries
  usb: d

Certain about struct *usb_otg at struct usb_phy

Peter Chen — 2012-05-24T09:27:10

Hi Felipe and others,

I have found one design limitation at current otg/phy framework, that
is there is a usb_otg pointer at usb_phy's struct, and we must keep it
in order to let the host and device driver pass their pointer to otg
driver (the otg driver here is mainly do dual-role switch, and with/
without otg timer funtion) through otg_set_host/otg_set_peripheral.

In fact, the struct usb_phy should be no relationship with struct usb_otg,
as phy and otg is no relationship, besides, the host/device driver
should unnecessary to call get_usb_transciever to get usb_phy's pointer.
usb phy is resource that any USB drivers can use it,  but should not 
mandatory use it.

I wonder if we can use some ways to delete usb_otg pointer from struct
usb_otg.

[PATCH] USB: qcserial: Add Sierra Wireless device IDs

Bjørn Mork — 2012-05-24T09:19:04

Some additional IDs found in the BSD/GPL licensed out-of-tree
GobiSerial driver from Sierra Wireless.

Signed-off-by: Bjørn Mork <bjorn-yOkvZcmFvRU< at >public.gmane.org>
---
 drivers/usb/serial/qcserial.c |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/drivers/usb/serial/qcserial.c b/drivers/usb/serial/qcserial.c
index 0d5fe59..996015c 100644
--- a/drivers/usb/serial/qcserial.c
+++ b/drivers/usb/serial/qcserial.c
< at >< at > -105,7 +105,13 < at >< at > static const struct usb_device_id id_table[] = {
 {USB_DEVICE(0x1410, 0xa021)},/* Novatel Gobi 3000 Composite */
 {USB_DEVICE(0x413c, 0x8193)},/* Dell Gobi 3000 QDL */
 {USB_DEVICE(0x413c, 0x8194)},/* Dell Gobi 3000 Composite */
+{USB_DEVICE(0x1199, 0x9010)},/* Sierra Wireless Gobi 3000 QDL */
+{USB_DEVICE(0x1199, 0x9012)},/* Sierra Wireless Gobi 3000 QDL */
 {USB_DEVICE(0x1199, 0x9013)},/* Sierra Wireless Gobi 3000 Modem device (MC8355) */
+{USB_DEVICE(0x1199, 0x9014)},/* Sierra Wireless Gobi 3000 QDL */
+{USB_DEVICE(0x1199, 0x9015)},/

[PATCH v2 0/4] usb: chipidea: correct naming and id management

Richard Zhao — 2012-05-23T15:45:14

Changes since v1:
 - rebase to Alex's tree for-felipe
 - add ci13xxx_remove_device to put id
 - change id management to bitmap

Richard Zhao (4):
  USB: Chipidea: rename struct ci13xxx_udc_driver to struct
    ci13xxx_platform_data
  USB: Chipidea: rename struct ci13xxx variables from udc to ci
  USB: Chipidea: add unified ci13xxx_{add,remove}_device for platform
    drivers
  USB: Chipidea: add ci13xxx device id management

 drivers/usb/chipidea/ci.h          |   30 +-
 drivers/usb/chipidea/ci13xxx_msm.c |   48 +--
 drivers/usb/chipidea/ci13xxx_pci.c |   52 +---
 drivers/usb/chipidea/core.c        |  108 ++++++-
 drivers/usb/chipidea/debug.c       |  146 +++++-----
 drivers/usb/chipidea/host.c        |    2 +-
 drivers/usb/chipidea/udc.c         |  630 ++++++++++++++++++------------------
 include/linux/usb/chipidea.h       |   11 +-
 8 files changed, 544 insertions(+), 483 deletions(-)

[PATCH] usb: chipidea: remove unneeded NULL check

Alexander Shishkin — 2012-05-23T13:00:56

As reported by Dan Carpenter, there is a NULL check in udc_start() that
follows a dereference of the pointer that's being checked. However, at
that point udc pointer shouldn't ever be NULL and if it is, the dereference
should cause an oops.

Reported-by: Dan Carpenter <dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA< at >public.gmane.org>
Signed-off-by: Alexander Shishkin <alexander.shishkin-VuQAYsv1563Yd54FQh9/CA< at >public.gmane.org>
---
 drivers/usb/chipidea/udc.c |    3 ---
 1 file changed, 3 deletions(-)

diff --git a/drivers/usb/chipidea/udc.c b/drivers/usb/chipidea/udc.c
index 51f9694..cdb9212 100644
--- a/drivers/usb/chipidea/udc.c
+++ b/drivers/usb/chipidea/udc.c
< at >< at > -1647,9 +1647,6 < at >< at > static int udc_start(struct ci13xxx *udc)
 struct device *dev = udc->dev;
 int retval = 0;
 
-if (!udc)
-return -EINVAL;

[PATCH] [g_mass_storage] Fix unmount problem with OS-X

Pantelis Antoniou — 2012-05-24T11:49:03

OS-X uses a sequence on unmounting that makes us close the backing
file. Apparently there's no way to open it again, which makes it
impossible to remount without rmmod'ing g_mass_storage.

Fix this by adding a media_ejected flag to each lun, and keeping
track of it properly.

Any other method (i.e. preventing unmount, and not keeping track
of the eject status) failed due to OS-X sending start stop commands
after the unmount and checking again.
---
 drivers/usb/gadget/f_mass_storage.c |   21 ++++++++++++++-------
 drivers/usb/gadget/storage_common.c |   11 +++++++++++
 2 files changed, 25 insertions(+), 7 deletions(-)

diff --git a/drivers/usb/gadget/f_mass_storage.c b/drivers/usb/gadget/f_mass_storage.c
index cb8c162..b865d20 100644
--- a/drivers/usb/gadget/f_mass_storage.c
+++ b/drivers/usb/gadget/f_mass_storage.c
< at >< at > -1445,6 +1445,9 < at >< at > static int do_start_stop(struct fsg_common *common)
 curlun->sense_data = SS_MEDIUM_NOT_PRESENT;
 return -EINVAL;
 }
+
+/* if the host is trying again, the media ar

[PATCH] drivers: usb: musb: add bf60x support

Bob Liu — 2012-05-23T10:09:49

Bf60x uses new musb ip which is a little different from old blackfin boards.
Now it's the same as most of other arch without a lot of blackfin specific
anomaly.

Signed-off-by: Bob Liu <lliubbo-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>
---
 drivers/usb/musb/Kconfig     |    3 ++-
 drivers/usb/musb/blackfin.c  |   31 +++++++++++++++++++++++++------
 drivers/usb/musb/musb_core.c |    5 +++--
 drivers/usb/musb/musb_core.h |    2 +-
 drivers/usb/musb/musb_dma.h  |    2 +-
 drivers/usb/musb/musb_io.h   |    2 +-
 drivers/usb/musb/musb_regs.h |    2 +-
 drivers/usb/musb/musbhsdma.c |    2 +-
 drivers/usb/musb/musbhsdma.h |    2 +-
 9 files changed, 36 insertions(+), 15 deletions(-)

diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig
index f70cab3..0fb1466 100644
--- a/drivers/usb/musb/Kconfig
+++ b/drivers/usb/musb/Kconfig
< at >< at > -7,6 +7,7 < at >< at >
 config USB_MUSB_HDRC
 tristate 'Inventra Highspeed Dual Role Controller (TI, ADI, ...)'
 depends on USB && USB_GADGET
+depends on (ARM || (BF54x && !BF544) || (B