From: Kishon Vijay Abraham I <kishon@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>, <tony@atomide.com>
Cc: <balbi@ti.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-usb@vger.kernel.org>, <tomi.valkeinen@ti.com>,
<linux@arm.linux.org.uk>, <eballetbo@gmail.com>,
<javier@dowhile0.org>, <gregkh@linuxfoundation.org>
Subject: Re: [RFC PATCH 1/4] arm: omap: Add phy binding info for musb in plat data
Date: Tue, 28 May 2013 10:48:02 +0530 [thread overview]
Message-ID: <51A43E0A.8090201@ti.com> (raw)
In-Reply-To: <1368796954-3499-1-git-send-email-kishon@ti.com>
Hi Tony,
On Friday 17 May 2013 06:52 PM, Kishon Vijay Abraham I wrote:
> In order for controllers to get PHY in case of non dt boot, the phy
> binding information (phy label) should be added in the platform
> data of the controller.
This series would be needed to get MUSB working in OMAP3 boards for
non-dt boot case. Do you think this is good enough to go in this rc cycle?
Thanks
Kishon
next prev parent reply other threads:[~2013-05-28 5:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 13:22 [RFC PATCH 1/4] arm: omap: Add phy binding info for musb in plat data Kishon Vijay Abraham I
2013-05-17 13:22 ` [RFC PATCH 2/4] usb: phy: add a new API to get PHY ref by label Kishon Vijay Abraham I
2013-05-17 13:22 ` [RFC PATCH 3/4] usb: musb: omap: use the new API to get PHY reference " Kishon Vijay Abraham I
2013-05-17 13:22 ` [RFC PATCH 4/4] arm: omap: remove using usb_bind_phy for binding musb and phy Kishon Vijay Abraham I
2013-05-28 5:18 ` Kishon Vijay Abraham I [this message]
2013-06-13 13:05 ` [RFC PATCH 1/4] arm: omap: Add phy binding info for musb in plat data Tomi Valkeinen
2013-06-14 5:35 ` Kishon Vijay Abraham I
2013-06-14 5:47 ` Tony Lindgren
2013-06-14 6:36 ` Tomi Valkeinen
2013-06-14 7:33 ` Tony Lindgren
2013-06-14 8:17 ` Tomi Valkeinen
2013-06-14 9:21 ` 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=51A43E0A.8090201@ti.com \
--to=kishon@ti.com \
--cc=balbi@ti.com \
--cc=eballetbo@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=javier@dowhile0.org \
--cc=linux-arm-kernel@lists.infradead.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=tomi.valkeinen@ti.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