mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: <gregkh@linuxfoundation.org>, <kishon@ti.com>,
	<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-usb@vger.kernel.org>, <balbi@ti.com>
Subject: [PATCH v3 0/5] usb: musb: cleanup
Date: Fri, 22 Jun 2012 17:40:50 +0530	[thread overview]
Message-ID: <1340367055-19835-1-git-send-email-kishon@ti.com> (raw)

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@ti.com>
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


             reply	other threads:[~2012-06-22 12:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 12:10 Kishon Vijay Abraham I [this message]
2012-06-22 12:10 ` [PATCH v3 1/5] usb: musb: move work_struct(otg_notifier_work) from core to omap glue Kishon Vijay Abraham I
2012-06-22 12:10 ` [PATCH v3 2/5] usb: musb: twl: use mailbox API to send VBUS or ID events Kishon Vijay Abraham I
2012-07-03 17:39   ` Matcovschi, Oleg
2012-07-04  5:47     ` ABRAHAM, KISHON VIJAY
2012-07-06  5:52       ` Matcovschi, Oleg
2012-06-22 12:10 ` [PATCH v3 3/5] drivers: usb: musb: move otg specific initializations from twl to glue Kishon Vijay Abraham I
2012-06-22 12:10 ` [PATCH v3 4/5] usb: musb: omap: use devres API to allocate resources Kishon Vijay Abraham I
2012-06-22 12:10 ` [PATCH v3 5/5] drivers: usb: otg: twl: " Kishon Vijay Abraham I

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1340367055-19835-1-git-send-email-kishon@ti.com \
    --to=kishon@ti.com \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®