From: Felipe Balbi <balbi@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: <rob.herring@calxeda.com>, <rob@landley.net>, <tony@atomide.com>,
<balbi@ti.com>, <b-cousson@ti.com>, <linux-usb@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-doc@vger.kernel.org>,
<devicetree-discuss@lists.ozlabs.org>,
<grant.likely@secretlab.ca>, <linux@arm.linux.org.uk>,
<gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2 2/4] ARM: OMAP: devices: create device for usb part of control module
Date: Wed, 23 Jan 2013 13:24:22 +0200 [thread overview]
Message-ID: <20130123112422.GF29258@arwen.pp.htv.fi> (raw)
In-Reply-To: <1358777308-2409-3-git-send-email-kishon@ti.com>
[-- Attachment #1: Type: text/plain, Size: 473 bytes --]
Hi,
On Mon, Jan 21, 2013 at 07:38:26PM +0530, Kishon Vijay Abraham I wrote:
> A seperate driver has been added to handle the usb part of control
> module. A device for the above driver is created here, using the register
> address information to be used by the driver for powering on the PHY and
> for writing to the mailbox.
>
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
Tony ? Without this we won't have the control module driver.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-23 11:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 14:08 [PATCH v2 0/4] usb: musb: add driver for " Kishon Vijay Abraham I
2013-01-21 14:08 ` [PATCH v2 1/4] drivers: usb: phy: add a new driver for usb part of " Kishon Vijay Abraham I
2013-01-21 14:08 ` [PATCH v2 2/4] ARM: OMAP: devices: create device " Kishon Vijay Abraham I
2013-01-23 11:24 ` Felipe Balbi [this message]
2013-02-01 19:16 ` Tony Lindgren
2013-01-21 14:08 ` [PATCH v2 3/4] ARM: OMAP2: MUSB: Specify omap4 has mailbox Kishon Vijay Abraham I
2013-01-21 14:08 ` [PATCH v2 4/4] drivers: usb: start using the control module driver 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=20130123112422.GF29258@arwen.pp.htv.fi \
--to=balbi@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--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=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
Powered by JetHome