From: gaku.inami.xw@bp.renesas.com (Gaku Inami)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: shmobile: add cpufreq-cpu0 driver for common SH-Mobile
Date: Wed, 25 Jun 2014 09:41:30 +0900 [thread overview]
Message-ID: <53AA1ABA.8070601@bp.renesas.com> (raw)
In-Reply-To: <20140623120811.GA2795@verge.net.au>
(2014/06/23 21:08), Simon Horman wrote:
> On Mon, Jun 23, 2014 at 09:38:09AM +0530, Viresh Kumar wrote:
>> On Mon, Jun 23, 2014 at 7:55 AM, Simon Horman
>> <horms+renesas@verge.net.au> wrote:
>>> diff --git a/arch/arm/mach-shmobile/cpufreq.c b/arch/arm/mach-shmobile/cpufreq.c
>>> +int __init shmobile_cpufreq_init(void)
>>> +{
>>> + struct device_node *np;
>>> +
>>> + np = of_cpu_device_node_get(0);
>>> + if (np == NULL) {
>>> + pr_err("failed to find cpu0 node\n");
>>> + return 0;
>>> + }
>>> +
>>> + if (of_get_property(np, "operating-points", NULL))
>> Probably you don't need any of above checks as these are done from
>> cpufreq-cpu0 probe as well.. So, simply create a platform device and
>> let cpufreq-cpu0 driver decide its fate.
> Thanks.
>
> Inami-san, could you look into this and make an incremental
> patch as appropriate?
Thank you for your feedback.
I will make an incremental patch based on renesas-devel-v3.16-rc2-20140623.
next prev parent reply other threads:[~2014-06-25 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 2:25 [GIT PULL] Renesas ARM Based SoC Cpufreq Updates for v3.17 Simon Horman
2014-06-23 2:25 ` [PATCH] ARM: shmobile: add cpufreq-cpu0 driver for common SH-Mobile Simon Horman
2014-06-23 4:08 ` Viresh Kumar
2014-06-23 12:08 ` Simon Horman
2014-06-25 0:41 ` Gaku Inami [this message]
2014-07-07 0:09 ` [GIT PULL] Renesas ARM Based SoC Cpufreq Updates for v3.17 Olof Johansson
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=53AA1ABA.8070601@bp.renesas.com \
--to=gaku.inami.xw@bp.renesas.com \
--cc=linux-arm-kernel@lists.infradead.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).