From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: "Rajendra Nayak" <rnayak@ti.com>,
"Kevin Hilman" <khilman@linaro.org>,
linux-omap <linux-omap@vger.kernel.org>,
"Rob Herring" <robherring2@gmail.com>,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
"Paul Walmsley" <paul@pwsan.com>,
"Benoît Cousson" <b-cousson@ti.com>,
"Jon Hunter" <jon-hunter@ti.com>, Keerthy <j-keerthy@ti.com>,
"Santosh Shilimkar" <santosh.shilimkar@ti.com>,
"Shawn Guo" <shawn.guo@linaro.org>
Subject: Re: [PATCH V3 1/2] ARM: OMAP3+: use cpu0-cpufreq driver in device tree supported boot
Date: Fri, 5 Apr 2013 15:17:55 -0700 [thread overview]
Message-ID: <20130405221755.GI10155@atomide.com> (raw)
In-Reply-To: <20130405221041.GA8648@kahuna>
* Nishanth Menon <nm@ti.com> [130405 15:15]:
> How does the following look?
> Option a) not have a dummy node if CPUFREQ_CPU0 is not configured:
> static inline void omap_init_cpufreq(void)
> {
> struct platform_device_info devinfo = { };
>
> if (!of_have_populated_dt())
> devinfo.name = "omap-cpufreq";
> else if (IS_ENABLED(CONFIG_GENERIC_CPUFREQ_CPU0))
> devinfo.name = "cpufreq-cpu0"
>
> if (devinfo.name)
> platform_device_register_full(&devinfo);
> }
>
> Option b) leave a dummy node registered
> static inline void omap_init_cpufreq(void)
> {
> struct platform_device_info devinfo = { };
>
> if (!of_have_populated_dt())
> devinfo.name = "omap-cpufreq";
> else
> devinfo.name = "cpufreq-cpu0"
>
> platform_device_register_full(&devinfo);
> }
>
> If there are no objections to (b), I dont mind it either.
To me option (b) looks better as it's if else :)
Tony
next prev parent reply other threads:[~2013-04-05 22:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 21:52 [PATCH V3 0/2] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot Nishanth Menon
2013-03-28 21:52 ` [PATCH V3 1/2] ARM: OMAP3+: use cpu0-cpufreq driver in device tree supported boot Nishanth Menon
2013-04-03 18:47 ` Kevin Hilman
2013-04-04 2:52 ` Nishanth Menon
2013-04-04 5:13 ` Rajendra Nayak
2013-04-04 19:00 ` Nishanth Menon
2013-04-05 9:50 ` Rajendra Nayak
2013-04-05 11:26 ` Nishanth Menon
2013-04-05 16:13 ` Tony Lindgren
2013-04-05 16:32 ` Nishanth Menon
2013-04-05 17:05 ` Tony Lindgren
2013-04-05 17:17 ` Nishanth Menon
2013-04-05 19:28 ` Tony Lindgren
2013-04-05 20:02 ` Nishanth Menon
2013-04-05 21:10 ` Tony Lindgren
2013-04-05 21:32 ` Nishanth Menon
2013-04-05 21:40 ` Tony Lindgren
2013-04-05 22:10 ` Nishanth Menon
2013-04-05 22:17 ` Tony Lindgren [this message]
2013-04-05 22:23 ` Nishanth Menon
2013-03-28 21:52 ` [PATCH V3 2/2] cpufreq: OMAP: instantiate omap-cpufreq as a platform_driver Nishanth Menon
2013-03-29 2:59 ` Viresh Kumar
2013-04-05 17:07 ` Nishanth Menon
2013-04-05 21:34 ` Kevin Hilman
2013-04-05 21:36 ` Nishanth Menon
2013-04-03 17:47 ` [PATCH V3 0/2] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot Kevin Hilman
2013-04-03 18:22 ` Nishanth Menon
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=20130405221755.GI10155@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=cpufreq@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=jon-hunter@ti.com \
--cc=khilman@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=robherring2@gmail.com \
--cc=santosh.shilimkar@ti.com \
--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).