[PATCH 3/3] arm/dt: tegra: add dts file for paz00
From: Stephen Warren <hidden>
Date: 2011-10-25 05:16:15
Also in:
linux-devicetree, linux-tegra
Possibly related (same subject, not in this thread)
- 2011-11-01 · [PATCH 3/3] arm/dt: tegra: add dts file for paz00 · Stephen Warren <hidden>
- 2011-11-01 · [PATCH 3/3] arm/dt: tegra: add dts file for paz00 · marvin24@gmx.de (Marc Dietrich)
- 2011-10-31 · [PATCH 3/3] arm/dt: tegra: add dts file for paz00 · marvin24@gmx.de (Marc Dietrich)
- 2011-10-31 · [PATCH 3/3] arm/dt: tegra: add dts file for paz00 · Stephen Warren <hidden>
- 2011-10-31 · [PATCH 3/3] arm/dt: tegra: add dts file for paz00 · marvin24@gmx.de (Marc Dietrich)
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.
...
quoted hunk
+++ 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.
quoted hunk
@@ -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? ...
+ i2c at 7000c500 {
+ clock-frequency = <80000>;That's a pretty odd I2C frequency... -- nvpublic