From: Nishanth Menon <nm@ti.com>
To: Christoph Fritz <chf.fritz@googlemail.com>,
Tony Lindgren <tony@atomide.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
bcousson@baylibre.com, Archit Taneja <archit@ti.com>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Daniel Mack <zonque@gmail.com>, "Hans J. Koch" <hjk@hansjkoch.de>
Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/6] ARM: dts: Add CPU OPP table for omap37xx100
Date: Tue, 21 Jan 2014 13:58:19 -0600 [thread overview]
Message-ID: <52DED15B.10502@ti.com> (raw)
In-Reply-To: <1390333660-30573-2-git-send-email-chf.fritz@googlemail.com>
On 01/21/2014 01:47 PM, Christoph Fritz wrote:
> This patch adds file omap37xx100.dtsi which includs a SoC specific table
> for CPU OPP.
>
> Please keep in mind that am/dm37xx100 variants differ from am/dm37xx
> SoCs without nomenclature marker prefix "100". This marker indicates
> the maximum cpu frequency. 100 stands for 1 GHz-Cortex-A8, blank means
> maximum 800 MHz.
>
> For more info, see Datasheet http://www.ti.com/lit/ds/sprs685d/sprs685d.pdf
> section 7.2.1 "Device and Development-Support Tool Nomenclature".
>
> Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
> ---
> arch/arm/boot/dts/omap37xx100.dtsi | 44 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 44 insertions(+)
> create mode 100644 arch/arm/boot/dts/omap37xx100.dtsi
>
> diff --git a/arch/arm/boot/dts/omap37xx100.dtsi b/arch/arm/boot/dts/omap37xx100.dtsi
> new file mode 100644
> index 0000000..064661e
> --- /dev/null
> +++ b/arch/arm/boot/dts/omap37xx100.dtsi
> @@ -0,0 +1,44 @@
> +/*
> + * Device Tree Source for OMAP37x SoC
> + *
> + * This file is licensed under the terms of the GNU General Public License
> + * version 2. This program is licensed "as is" without any warranty of any
> + * kind, whether express or implied.
> + */
> +
> +#include "omap3.dtsi"
> +
> +/ {
> + aliases {
> + serial3 = &uart4;
> + };
> +
> + cpus {
> + /* AM/DM37xx */
> + cpu@0 {
> + operating-points = <
> + /* kHz uV */
> + 125000 975000
> + 250000 1075000
> + 500000 1100000
> + 600000 1140000
> + 800000 1270000
> + 1000000 1380000
This is valid even for 3630/DM3730 as well -> unfortunately - you
cannot enable 1GHz without enabling ABB and AVS 1.5.
There is a bunch of internal discussion with respect to lack of this
information available.. but as it stands right now, I dont think this
is valid.
> + >;
> + clock-latency = <300000>; /* From legacy driver */
> + };
> + };
> +
> + ocp {
> + /* uart4 is only available on CBP and CBC packages */
> + uart4: serial@49042000 {
> + compatible = "ti,omap3-uart";
> + reg = <0x49042000 0x400>;
> + interrupts = <80>;
> + dmas = <&sdma 81 &sdma 82>;
> + dma-names = "tx", "rx";
> + ti,hwmods = "uart4";
> + clock-frequency = <48000000>;
> + };
> + };
> +};
>
Further, we should be able to reuse 3630.dtsi for this.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-01-21 19:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 19:47 [PATCH 0/6] ARM: add omap3 INCOstartec board support Christoph Fritz
2014-01-21 19:47 ` [PATCH 1/6] ARM: dts: Add CPU OPP table for omap37xx100 Christoph Fritz
2014-01-21 19:58 ` Nishanth Menon [this message]
2014-01-21 19:47 ` [PATCH 2/6] ARM: dts: omap3: Add support for INCOstartec a83x module Christoph Fritz
2014-01-21 19:47 ` [PATCH 3/6] ARM: dts: omap3: Add support for INCOstartec DBB056 baseboard Christoph Fritz
2014-01-21 19:47 ` [PATCH 4/6] ARM: OMAP2+: add legacy display for omap3 DBB056 Christoph Fritz
2014-01-22 0:10 ` Javier Martinez Canillas
2014-01-22 0:24 ` Sebastian Reichel
[not found] ` <20140122002435.GA7943-SfvFxonMDyemK9LvCR3Hrw@public.gmane.org>
2014-01-22 0:26 ` Javier Martinez Canillas
2014-01-21 19:47 ` [PATCH 5/6] ARM: OMAP2+: Add pdata quirk for sys_clkout2 " Christoph Fritz
2014-01-21 21:18 ` Nishanth Menon
2014-01-21 19:47 ` [PATCH 6/6] [RFC] omapdss: remove FEAT_DPI_USES_VDDS_DSI from omap3 Christoph Fritz
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=52DED15B.10502@ti.com \
--to=nm@ti.com \
--cc=archit@ti.com \
--cc=bcousson@baylibre.com \
--cc=chf.fritz@googlemail.com \
--cc=devicetree@vger.kernel.org \
--cc=hjk@hansjkoch.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.com \
--cc=zonque@gmail.com \
/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).