From: Roger Quadros <rogerq@ti.com>
To: Sascha Hauer <s.hauer@pengutronix.de>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Rajendra Nayak <rnayak@ti.com>
Cc: <tony@atomide.com>, Russell King <linux@arm.linux.org.uk>,
<devicetree-discuss@lists.ozlabs.org>,
<linux-kernel@vger.kernel.org>, <balbi@ti.com>,
<linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] ARM: OMAP2+: Allow clock alias provision from device tree
Date: Tue, 12 Feb 2013 09:47:40 +0200 [thread overview]
Message-ID: <5119F39C.2080206@ti.com> (raw)
In-Reply-To: <20130211160752.GG1906@pengutronix.de>
On 02/11/2013 06:07 PM, Sascha Hauer wrote:
> On Mon, Feb 11, 2013 at 05:44:23PM +0200, Roger Quadros wrote:
>> Currently on OMAP, it is not possible to specify a clock consumer
>> to any of the OMAP generated clocks using the device tree. This can pose
>> a problem for external devices that run off an OMAP clock as we
>> can't reliably provide a reference to the clock in the device tree.
>
> There is an established way of providing clocks in the devicetree using
> the clocks/clock-names properties. Wouldn't it be better using this
> for OMAP aswell?
>
I agree with you, but I'm not sure when this migration will be done.
Rajendra/Santosh might know better.
regards,
-roger
prev parent reply other threads:[~2013-02-12 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 15:44 [PATCH 1/2] ARM: OMAP2+: Allow clock alias provision from device tree Roger Quadros
2013-02-11 15:44 ` [PATCH 2/2] ARM: dts: omap4-panda: Add clock alias for USB PHY Roger Quadros
2013-02-11 15:49 ` [PATCH 1/2] ARM: OMAP2+: Allow clock alias provision from device tree Felipe Balbi
2013-02-11 16:07 ` Sascha Hauer
2013-02-12 7:47 ` Roger Quadros [this message]
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=5119F39C.2080206@ti.com \
--to=rogerq@ti.com \
--cc=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rnayak@ti.com \
--cc=s.hauer@pengutronix.de \
--cc=santosh.shilimkar@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;
as well as URLs for NNTP newsgroup(s).