From: Kishon Vijay Abraham I <kishon@ti.com>
To: balbi@ti.com, kishon@ti.com, grant.likely@secretlab.ca,
rob.herring@calxeda.com, rob@landley.net, linux@arm.linux.org.uk,
gregkh@linuxfoundation.org, b-cousson@ti.com, rnayak@ti.com,
tony@atomide.com, devicetree-discuss@lists.ozlabs.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: [PATCH v2 0/3] omap: musb: Add device tree support
Date: Tue, 11 Sep 2012 14:39:37 +0530 [thread overview]
Message-ID: <1347354580-5895-1-git-send-email-kishon@ti.com> (raw)
This patch series adds device tree support for MUSB.
The glue layer is now made to write to mailbox register (present in
control module) instead of calling phy layer to write to mailbox
register. Writing to mailbox register notifies the core of events like
device connect/disconnect.
Changes from v1:
* Added a comment in hwmod data to remove the control module data from
otg_hs once control driver is in place.
* Fixed the omap-usb Documentation to the correct compatible value
(Should be "ti,omap4-musb" or "ti,omap3-musb")
Previously these patches were part of
[PATCH v7 0/7] omap: musb: Add device tree support
This patch series was created to contain only the *musb* part and it
also has one hwmod patch.
This patch series was created on
git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git musb
Kishon Vijay Abraham I (3):
arm: omap: hwmod: add a new addr space in otg for writing to control
module
usb: musb: omap: write directly to mailbox instead of using phy
usb: musb: omap: Add device tree support for omap musb glue
Documentation/devicetree/bindings/usb/omap-usb.txt | 33 ++++++
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 6 ++
drivers/usb/musb/omap2430.c | 106 ++++++++++++++++++--
drivers/usb/musb/omap2430.h | 9 ++
4 files changed, 147 insertions(+), 7 deletions(-)
create mode 100644 Documentation/devicetree/bindings/usb/omap-usb.txt
--
1.7.9.5
next reply other threads:[~2012-09-11 9:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 9:09 Kishon Vijay Abraham I [this message]
2012-09-11 9:09 ` [PATCH v2 2/3] usb: musb: omap: write directly to mailbox instead of using phy Kishon Vijay Abraham I
[not found] ` <1347354580-5895-1-git-send-email-kishon-l0cyMroinI0@public.gmane.org>
2012-09-11 9:09 ` [PATCH v2 1/3] arm: omap: hwmod: add a new addr space in otg for writing to control module Kishon Vijay Abraham I
2012-09-11 9:13 ` Benoit Cousson
2012-09-11 9:09 ` [PATCH v2 3/3] usb: musb: omap: Add device tree support for omap musb glue Kishon Vijay Abraham I
[not found] ` <1347354580-5895-4-git-send-email-kishon-l0cyMroinI0@public.gmane.org>
2012-09-11 9:53 ` Vaibhav Hiremath
2012-09-11 11:24 ` ABRAHAM, KISHON VIJAY
[not found] ` <CAAe_U6LwGn+qbSox7BofTg7sJUxqytew3s_73MOYZytHs2qEWw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-09-11 11:34 ` Hiremath, Vaibhav
2013-01-08 19:32 ` Sergei Shtylyov
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=1347354580-5895-1-git-send-email-kishon@ti.com \
--to=kishon@ti.com \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rnayak@ti.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=tony@atomide.com \
/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;
as well as URLs for NNTP newsgroup(s).