From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: cpufreq <cpufreq@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Shawn Guo <shawn.guo@linaro.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] cpufreq: cpufreq-cpu0: support for clock which are not in DT yet.
Date: Tue, 12 Mar 2013 10:33:00 +0530 [thread overview]
Message-ID: <513EB704.8030907@ti.com> (raw)
In-Reply-To: <1363043130-30270-2-git-send-email-nm@ti.com>
On Tuesday 12 March 2013 04:35 AM, Nishanth Menon wrote:
> On certain SoCs like variants of OMAP, the clock conversion to DT
> is not complete. In short, the ability to:
> cpus {
> cpu@0 {
> clocks = <&cpuclk 0>;
> };
> };
> is not possible. However, the clock node is registered.
> Allow for clk names to be provided as string so as to be used when needed.
> Example (for OMAP3630):
> cpus {
> cpu@0 {
> clock-name = "cpufreq_ck";
> };
> };
>
> Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Cc: Shawn Guo <shawn.guo@linaro.org>
> Cc: linux-kernel@vger.kernel.org
> Cc: cpufreq@vger.kernel.org
> Cc: linux-pm@vger.kernel.org
> Cc: linux-omap@vger.kernel.org
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
Seems a reasonable to me.
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
next prev parent reply other threads:[~2013-03-12 5:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 23:05 [PATCH 0/2] cpufreq: cpufreq-cpu0: cleanups around DT usage Nishanth Menon
2013-03-11 23:05 ` [PATCH 1/2] cpufreq: cpufreq-cpu0: support for clock which are not in DT yet Nishanth Menon
2013-03-12 5:03 ` Santosh Shilimkar [this message]
2013-03-12 14:24 ` Benoit Cousson
2013-03-12 14:35 ` Nishanth Menon
2013-03-12 15:17 ` J, KEERTHY
2013-03-12 15:51 ` Nishanth Menon
2013-03-12 7:36 ` Shawn Guo
2013-03-11 23:05 ` [PATCH 2/2] cpufreq: cpufreq-cpu0: provide compatibility string for DT matchup Nishanth Menon
2013-03-12 5:07 ` Santosh Shilimkar
2013-03-12 14:28 ` Benoit Cousson
2013-03-12 14:35 ` Santosh Shilimkar
2013-03-12 14:43 ` Nishanth Menon
2013-03-12 15:31 ` Benoit Cousson
[not found] ` <1363043130-30270-3-git-send-email-nm-l0cyMroinI0@public.gmane.org>
2013-03-12 7:57 ` Shawn Guo
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=513EB704.8030907@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@sisk.pl \
--cc=shawn.guo@linaro.org \
/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).