From: marvin24@gmx.de (Marc Dietrich)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] arm/dt: tegra: add dts file for paz00
Date: Tue, 25 Oct 2011 21:05:08 +0200 [thread overview]
Message-ID: <2821699.TeokzqUUds@ax5200p> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF173E1B4189@HQMAIL01.nvidia.com>
On Monday 24 October 2011 22:16:15 Stephen Warren wrote:
> Marc Dietrich wrote at Saturday, October 22, 2011 2:17 PM:
> > * NOT FOR COMMIT *
> >
> > This just adds the dts for paz00. I like to add it to board-dt as
> > well as soon as I find out which tree to base it on.
>
> ...
>
> > +++ b/arch/arm/boot/dts/tegra-paz00.dts
>
> One thing that cross my mind when writing the TrimSlice support and I
> forgot to mention: Should these files be named ${soc}-${board}.dts or
> ${vendor}-${board}.dts (tegra-paz00.dts or toshiba-paz00.dts or
> compal-paz00.dts). I'm OK either way; just want to follow any outside
> expectations.
I also don't know. I prefer compal for paz00 because Toshiba's code name was
procyon (I think) and I don't want to change all the naming. Also Toshiba
showed no interest in helping us, so I don't see why they should get the fame.
> > @@ -0,0 +1,51 @@
> > +/dts-v1/;
> > +
> > +/memreserve/ 0x1c000000 0x04000000;
> > +/include/ "tegra20.dtsi"
> > +
> > +/ {
> > + model = "Toshiba AC100 / Dynabook AZ";
> > + compatible = "compal,paz00", "nvidia,tegra20";
> > +
> > + chosen {
> > + bootargs = "console=ttyS0,115200n8 root=/dev/mmcblk1p1";
> > + };
> > +
> > + memory at 0 {
>
> The other boards just have "memory" here; which is wrong?
I just copy-pasted from harmony, I guess it doesn't matter.
>
> ...
>
> > + i2c at 7000c500 {
> > + clock-frequency = <80000>;
>
> That's a pretty odd I2C frequency...
no, 80000 is even ;-) Seriously, it just reflects the fact that the embedded
controller bus runs at 80kHz. Even more seriously, reading "booting-without-
of.txt" in the Documentation/devicetree dir,
| o PowerPC,970 at 0
| |- name = "PowerPC,970"
| |- device_type = "cpu"
| |- reg = <0>
| |- clock-frequency = <5f5e1000>
| |- 64-bit
| |- linux,phandle = <2>
it looks like all clock-frequency values are hexadecimal. In this case even
<400000> would be wrong (or the docu is --- ok, the docu is wrong).
Marc
next prev parent reply other threads:[~2011-10-25 19:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1319313019.git.marvin24@gmx.de>
[not found] ` <90ee88bcde84141e0280ffa4ccbd288462489eba.1319313020.git.marvin24@gmx.de>
2011-10-25 5:16 ` [PATCH 3/3] arm/dt: tegra: add dts file for paz00 Stephen Warren
2011-10-25 19:05 ` Marc Dietrich [this message]
2011-10-26 6:43 ` Stephen Warren
2011-10-26 20:18 ` Marc Dietrich
2011-10-25 19:51 ` Rob Herring
2011-10-26 6:40 ` Stephen Warren
2011-10-31 19:58 [PATCH v3 0/3] paz00 updates for 3.3 Marc Dietrich
2011-10-31 19:58 ` [PATCH 3/3] arm/dt: tegra: add dts file for paz00 Marc Dietrich
2011-10-31 20:14 ` Stephen Warren
2011-10-31 22:20 ` Marc Dietrich
-- strict thread matches above, loose matches on Subject: below --
2011-11-01 20:37 [PATCH v4 0/3] paz00 updates for 3.3 Marc Dietrich
2011-11-01 20:37 ` [PATCH 3/3] arm/dt: tegra: add dts file for paz00 Marc Dietrich
2011-11-01 22:37 ` Stephen Warren
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=2821699.TeokzqUUds@ax5200p \
--to=marvin24@gmx.de \
--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