From: Jon Hunter <jon-hunter@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: linux-omap@vger.kernel.org,
"Kevin Hilman" <khilman@deeprootsystems.com>,
"Benoît Cousson" <b-cousson@ti.com>,
"Santosh Shilimkar" <santosh.shilimkar@ti.com>,
"Shawn Guo" <shawn.guo@linaro.org>, Keerthy <j-keerthy@ti.com>,
devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 6/8] ARM: dts: OMAP446x: move CPU OPP tables to device tree
Date: Thu, 14 Mar 2013 16:49:34 -0500 [thread overview]
Message-ID: <514245EE.6090906@ti.com> (raw)
In-Reply-To: <1363294695-658-7-git-send-email-nm@ti.com>
On 03/14/2013 03:58 PM, Nishanth Menon wrote:
> OMAP4430 and 4460 have different OPP definitions. So, create an SoC
> variant dtsi file for 4460 and move the OPP definitions to it.
FYI, I had to create a similar file for PMU [1]. However, I called it
omap4460.dtsi and not omap446x.dtsi as there is only one omap446x
device. That should go into to v3.10 and so may be worth basing this on
top. I do like your omap4-panda-common.dtsi that is a nice clean-up.
Cheers
Jon
[1]
http://git.kernel.org/cgit/linux/kernel/git/bcousson/linux-omap-dt.git/commit/?h=for_3.10/dts&id=5e64b6b1137a54f353528d6da60071c1ef0043ba
WARNING: multiple messages have this Message-ID (diff)
From: jon-hunter@ti.com (Jon Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/8] ARM: dts: OMAP446x: move CPU OPP tables to device tree
Date: Thu, 14 Mar 2013 16:49:34 -0500 [thread overview]
Message-ID: <514245EE.6090906@ti.com> (raw)
In-Reply-To: <1363294695-658-7-git-send-email-nm@ti.com>
On 03/14/2013 03:58 PM, Nishanth Menon wrote:
> OMAP4430 and 4460 have different OPP definitions. So, create an SoC
> variant dtsi file for 4460 and move the OPP definitions to it.
FYI, I had to create a similar file for PMU [1]. However, I called it
omap4460.dtsi and not omap446x.dtsi as there is only one omap446x
device. That should go into to v3.10 and so may be worth basing this on
top. I do like your omap4-panda-common.dtsi that is a nice clean-up.
Cheers
Jon
[1]
http://git.kernel.org/cgit/linux/kernel/git/bcousson/linux-omap-dt.git/commit/?h=for_3.10/dts&id=5e64b6b1137a54f353528d6da60071c1ef0043ba
next prev parent reply other threads:[~2013-03-14 21:49 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 20:58 [PATCH 0/8] ARM: OMAP3+: Switch to use DT based cpu0-cpufreq driver Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 20:58 ` [PATCH 1/8] ARM: dts: OMAP34xx: move CPU OPP tables to device tree Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 21:43 ` Jon Hunter
2013-03-14 21:43 ` Jon Hunter
2013-03-14 20:58 ` [PATCH 2/8] ARM: dts: OMAP36xx: " Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 21:44 ` Jon Hunter
2013-03-14 21:44 ` Jon Hunter
2013-03-15 13:56 ` Nishanth Menon
2013-03-15 13:56 ` Nishanth Menon
2013-03-15 14:26 ` Jon Hunter
2013-03-15 14:26 ` Jon Hunter
2013-03-15 14:38 ` Nishanth Menon
2013-03-15 14:38 ` Nishanth Menon
2013-03-15 14:58 ` Jon Hunter
2013-03-15 14:58 ` Jon Hunter
2013-03-15 15:02 ` Nishanth Menon
2013-03-15 15:02 ` Nishanth Menon
2013-03-14 20:58 ` [PATCH 3/8] ARM: dts: OMAP3: use twl4030 vdd1 regulator for CPU Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 20:58 ` [PATCH 4/8] ARM: dts: OMAP443x: move CPU OPP tables to device tree Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 20:58 ` [PATCH 5/8] ARM: dts: omap4-panda: move generic sections to panda-common Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 20:58 ` [PATCH 6/8] ARM: dts: OMAP446x: move CPU OPP tables to device tree Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 21:49 ` Jon Hunter [this message]
2013-03-14 21:49 ` Jon Hunter
2013-03-15 14:08 ` Nishanth Menon
2013-03-15 14:08 ` Nishanth Menon
2013-03-14 20:58 ` [PATCH 7/8] ARM: OMAP3+: use cpu0-cpufreq driver Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 20:58 ` [PATCH 8/8] cpufreq: omap: remove omap-cpufreq Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-14 20:58 ` Nishanth Menon
2013-03-15 4:51 ` Viresh Kumar
2013-03-15 4:51 ` Viresh Kumar
2013-03-15 14:24 ` Nishanth Menon
2013-03-15 14:24 ` Nishanth Menon
2013-03-15 14:24 ` Nishanth Menon
2013-03-14 21:42 ` [PATCH 0/8] ARM: OMAP3+: Switch to use DT based cpu0-cpufreq driver Jon Hunter
2013-03-14 21:42 ` Jon Hunter
2013-03-15 13:52 ` Nishanth Menon
2013-03-15 13:52 ` Nishanth Menon
2013-03-15 5:18 ` Santosh Shilimkar
2013-03-15 5:18 ` Santosh Shilimkar
2013-03-15 14:21 ` Nishanth Menon
2013-03-15 14:21 ` Nishanth Menon
2013-03-15 14:56 ` Jon Hunter
2013-03-15 14:56 ` Jon Hunter
2013-03-15 15:00 ` Nishanth Menon
2013-03-15 15:00 ` 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=514245EE.6090906@ti.com \
--to=jon-hunter@ti.com \
--cc=b-cousson@ti.com \
--cc=cpufreq@vger.kernel.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=j-keerthy@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.