From: Kishon Vijay Abraham I <kishon@ti.com>
To: grant.likely@secretlab.ca, rob.herring@calxeda.com,
rob@landley.net, linux@arm.linux.org.uk, kishon@ti.com,
b-cousson@ti.com, rnayak@ti.com, tony@atomide.com,
gregkh@linuxfoundation.org, ohad@wizery.com,
linus.walleij@linaro.org, myungjoo.ham@samsung.com,
rusty@rustcorp.com.au, swarren@nvidia.com,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, balbi@ti.com,
linux-omap@vger.kernel.org, linux-usb@vger.kernel.org
Subject: [PATCH 0/2] omap: add ocp2scp as a bus driver
Date: Mon, 16 Jul 2012 19:43:41 +0530 [thread overview]
Message-ID: <1342448023-14438-1-git-send-email-kishon@ti.com> (raw)
This patch series is done as a preparatory step for adding phy drivers
for dwc3 and musb.
This series adds a new driver for ocp2scp (only dt) to which phy
drivers are connected.
Since currently there is no generic way to create a child device along
with doing a pm_runtime_enable (the exact requirement for ocp2scp), I'm
creating a separate driver for ocp2scp.
Changes from [RFC PATCH v2 0/2] omap: add ocp2scp as a misc driver:
Created a new folder drivers/bus and moved ocp2scp driver from misc to
drivers/bus.
This patch was developed and tested on
git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
Kishon Vijay Abraham I (2):
drivers: bus: add a new driver for omap-ocp2scp
arm/dts: omap4: Add ocp2scp data
.../devicetree/bindings/bus/omap-ocp2scp.txt | 10 ++
arch/arm/boot/dts/omap4.dtsi | 8 ++
drivers/Kconfig | 2 +
drivers/Makefile | 2 +
drivers/bus/Kconfig | 15 +++
drivers/bus/Makefile | 5 +
drivers/bus/omap-ocp2scp.c | 98 ++++++++++++++++++++
7 files changed, 140 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
create mode 100644 drivers/bus/Kconfig
create mode 100644 drivers/bus/Makefile
create mode 100644 drivers/bus/omap-ocp2scp.c
--
1.7.5.4
next reply other threads:[~2012-07-16 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 14:13 Kishon Vijay Abraham I [this message]
[not found] ` <1342448023-14438-1-git-send-email-kishon-l0cyMroinI0@public.gmane.org>
2012-07-16 14:13 ` [PATCH 1/2] drivers: bus: add a new driver for omap-ocp2scp Kishon Vijay Abraham I
2012-07-17 5:13 ` ABRAHAM, KISHON VIJAY
[not found] ` <CAAe_U6K9sm-sDK80ySSHPGf5SYuwDkhW+4q8r2deXi7Tz3TxJw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-17 8:00 ` Arnd Bergmann
2012-07-16 14:13 ` [PATCH 2/2] arm/dts: omap4: Add ocp2scp data Kishon Vijay Abraham I
2012-07-17 12:36 ` Sergei Shtylyov
2012-07-18 5:43 ` ABRAHAM, KISHON VIJAY
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=1342448023-14438-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=linus.walleij@linaro.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=myungjoo.ham@samsung.com \
--cc=ohad@wizery.com \
--cc=rnayak@ti.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=rusty@rustcorp.com.au \
--cc=swarren@nvidia.com \
--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).