[PATCH v3 0/5] usb: musb: cleanup

[Kishon Vijay Abraham I]

Most part of this patch series was obtained by splitting
[RFC PATCH 2/3] usb: musb: omap glue: use omap-usb2 as the phy driver.

TO DO:
* dt adaptation of musb omap glue, twl4030, twl6030.
* Use control module driver API to write to control module registers
 (mailbox and power control of phy)
* send usb2 phy driver
* make musb omap glue use usb2 phy driver and make twl630
 as a comparator driver.

Changes from v2:
* Added a condition in twl4030 to avoid spurious disconnect event
message to the omap glue, on bootup if the cable is not connected.

Changes from v1:
Changed the commit log of *usb: musb: move work_struct(otg_notifier_work)
from core to omap glue* as per Sergei's suggestion.

Patch series depends on
[PATCH v7 0/3] usb: multi-phy support

Developed and Tested on.
git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git musb

commit 2ed9127cff9a255b7671b8d3d938109f68a87961
Author: Mantesh Sarasetti <mantesh@xxxxxx>
Date:   Fri Jun 1 14:54:30 2012 +0300

    usb: musb: host: Disable MUSB DMA mode incase of DMA channel request failure

Performed device mode testing in omap4 panda and omap3 beagle.

Kishon Vijay Abraham I (5):
  usb: musb: move work_struct(otg_notifier_work) from core to omap glue
  usb: musb: twl: use mailbox API to send VBUS or ID events
  drivers: usb: musb: move otg specific initializations from twl to
    glue
  usb: musb: omap: use devres API to allocate resources
  drivers: usb: otg: twl: use devres API to allocate resources

 drivers/usb/musb/musb_core.h  |    2 -
 drivers/usb/musb/omap2430.c   |  122 +++++++++++++++++++++++++---------------
 drivers/usb/otg/twl4030-usb.c |   67 ++++++++--------------
 drivers/usb/otg/twl6030-usb.c |   69 ++++++++---------------
 include/linux/usb/musb-omap.h |   30 ++++++++++
 5 files changed, 155 insertions(+), 135 deletions(-)
 create mode 100644 include/linux/usb/musb-omap.h

-- 
1.7.5.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/