From: santosh.shilimkar@ti•com (Santosh Shilimkar)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH V2 8/8] cpufreq: OMAP: donot allow to be used with device tree
Date: Wed, 20 Mar 2013 11:47:50 +0530 [thread overview]
Message-ID: <5149548E.6030405@ti.com> (raw)
In-Reply-To: <1363715590-5131-9-git-send-email-nm@ti.com>
On Tuesday 19 March 2013 11:23 PM, Nishanth Menon wrote:
> We now use Soc generic cpufreq-cpu0 driver using DT entries.
> However to allow cpufreq-cpu0 and omap-cpufreq drivers to co-exist,
> we need to ensure the following using the same image:
> 1. With device tree boot, we use cpufreq-cpu0
> 2. With non device tree boot, we use omap-cpufreq
>
> In the case of (1), we will have cpu OPPs and regulator registered
> as part of the DT, to ensure that omap-cpufreq and cpufreq-cpu0 don't
> conflict in managing the frequency of the same cpu, we should not
> permit init to pass in omap-cpufreq.
>
> In the case of (2), we will not have the cpufreq-cpu0 device, hence
> only omap-cpufreq will be active.
>
> So, to acommodate both these usage conditions, we fail init of
> omap-cpufreq when we boot with device tree.
>
> Cc: Kevin Hilman <khilman@deeprootsystems•com>
> Cc: Jon Hunter <jon-hunter@ti•com>
> Cc: "Beno?t Cousson" <b-cousson@ti•com>
> Cc: Santosh Shilimkar <santosh.shilimkar@ti•com>
> Cc: Shawn Guo <shawn.guo@linaro•org>
> Cc: Keerthy <j-keerthy@ti•com>
> Cc: linux-omap at vger.kernel.org
> Cc: devicetree-discuss at lists.ozlabs.org
> Cc: linux-arm-kernel at lists.infradead.org
> Cc: cpufreq at vger.kernel.org
> Cc: linux-pm at vger.kernel.org
>
> Signed-off-by: Nishanth Menon <nm@ti•com>
> ---
I haven't followed all the DT binding for opp discussion but
this patch is inline to keep non-DT cpufreq working till we
move to DT only build.
So FWIW,
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti•com>
next prev parent reply other threads:[~2013-03-20 6:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 17:53 [PATCH V2 0/8] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot Nishanth Menon
2013-03-19 17:53 ` [PATCH V2 1/8] ARM: dts: OMAP34xx/35xx: Add CPU OPP table Nishanth Menon
2013-03-19 17:53 ` [PATCH V2 2/8] ARM: dts: OMAP36xx: " Nishanth Menon
2013-03-19 17:53 ` [PATCH V2 3/8] ARM: dts: OMAP3: use twl4030 vdd1 regulator for CPU Nishanth Menon
2013-03-19 17:53 ` [PATCH V2 4/8] ARM: dts: OMAP443x: Add CPU OPP table Nishanth Menon
2013-03-19 17:53 ` [PATCH V2 5/8] ARM: dts: omap4-panda: move generic sections to panda-common Nishanth Menon
2013-03-19 17:53 ` [PATCH V2 6/8] ARM: dts: OMAP4460: Add CPU OPP table Nishanth Menon
2013-03-19 17:53 ` [PATCH V2 7/8] ARM: OMAP3+: use cpu0-cpufreq driver in device tree supported boot Nishanth Menon
2013-03-19 17:53 ` [PATCH V2 8/8] cpufreq: OMAP: donot allow to be used with device tree Nishanth Menon
2013-03-20 6:17 ` Santosh Shilimkar [this message]
2013-03-27 18:39 ` Kevin Hilman
2013-03-27 20:59 ` Nishanth Menon
2013-03-27 20:37 ` [PATCH V2 0/8] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot Kevin Hilman
2013-03-28 11:03 ` Benoit Cousson
2013-03-28 13:43 ` Nishanth Menon
2013-03-28 15:49 ` Benoit Cousson
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=5149548E.6030405@ti.com \
--to=santosh.shilimkar@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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