diff for duplicates of <20150212160316.GL2531@atomide.com> diff --git a/a/1.txt b/N1/1.txt index 1c43ea5..fc2a971 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -30,7 +30,7 @@ the same offset between 34xx and 36xx variants? > +&i2c1 { > + clock-frequency = <2600000>; > + -> + twl: twl@48 { +> + twl: twl at 48 { > + reg = <0x48>; > + interrupts = <7>; /* SYS_NIRQ cascaded to intc */ > + interrupt-parent = <&intc>; @@ -62,7 +62,7 @@ a minimum of 16MB: ranges = <0 0 0x30000000 0x1000000>, /* CS0: 16MB for NAND */ -> + nand@0,0 { +> + nand at 0,0 { > + reg = <0 0 0>; /* CS0, offset 0 */ The reg is for the device driver to ioremap it's registers, @@ -70,7 +70,7 @@ for NAND it's just 4: reg = <0 0 4>; /* CS0, offset 0, IO size 4 */ -> + filesystem@680000 { +> + filesystem at 680000 { > + label = "rootfs"; > + reg = <0xc80000 0>; /* 0 = MTDPART_SIZ_FULL */ > + }; @@ -80,7 +80,7 @@ for NAND it's just 4: Is the NAND the same size on all of them? I don't think dts has a binding for MTDPART_SIZ_FULL type thing.. -> + lcd: lcd@1 { +> + lcd: lcd at 1 { > + reg = <1>; /* CS1 */ > + compatible = "omapdss,tpo,td043mtea1"; > + spi-max-frequency = <100000>; diff --git a/a/content_digest b/N1/content_digest index 8417232..34574f9 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,21 +1,9 @@ "ref\01423746226-700-1-git-send-email-marek@goldelico.com\0" "ref\01423746226-700-2-git-send-email-marek@goldelico.com\0" - "From\0Tony Lindgren <tony@atomide.com>\0" - "Subject\0Re: [PATCH 1/4] ARM: dts: omap3-pandora: add common device tree\0" + "From\0tony@atomide.com (Tony Lindgren)\0" + "Subject\0[PATCH 1/4] ARM: dts: omap3-pandora: add common device tree\0" "Date\0Thu, 12 Feb 2015 08:03:16 -0800\0" - "To\0Marek Belisko <marek@goldelico.com>\0" - "Cc\0bcousson@baylibre.com" - robh+dt@kernel.org - pawel.moll@arm.com - mark.rutland@arm.com - ijc+devicetree@hellion.org.uk - galak@codeaurora.org - devicetree@vger.kernel.org - linux@arm.linux.org.uk - linux-arm-kernel@lists.infradead.org - linux-kernel@vger.kernel.org - linux-omap@vger.kernel.org - " H. Nikolaus Schaller <hns@goldelico.com>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "Hi,\n" @@ -50,7 +38,7 @@ "> +&i2c1 {\n" "> +\tclock-frequency = <2600000>;\n" "> +\n" - "> +\ttwl: twl@48 {\n" + "> +\ttwl: twl at 48 {\n" "> +\t\treg = <0x48>;\n" "> +\t\tinterrupts = <7>; /* SYS_NIRQ cascaded to intc */\n" "> +\t\tinterrupt-parent = <&intc>;\n" @@ -82,7 +70,7 @@ "\n" "\tranges = <0 0 0x30000000 0x1000000>,\t/* CS0: 16MB for NAND */\n" "\n" - "> +\tnand@0,0 {\n" + "> +\tnand at 0,0 {\n" "> +\t\treg = <0 0 0>; /* CS0, offset 0 */\n" "\n" "The reg is for the device driver to ioremap it's registers,\n" @@ -90,7 +78,7 @@ "\n" "\t\treg = <0 0 4>;\t/* CS0, offset 0, IO size 4 */\n" "\n" - "> +\t\tfilesystem@680000 {\n" + "> +\t\tfilesystem at 680000 {\n" "> +\t\t\tlabel = \"rootfs\";\n" "> +\t\t\treg = <0xc80000 0>;\t/* 0 = MTDPART_SIZ_FULL */\n" "> +\t\t};\n" @@ -100,7 +88,7 @@ "Is the NAND the same size on all of them? I don't think dts\n" "has a binding for MTDPART_SIZ_FULL type thing..\n" "\n" - "> +\tlcd: lcd@1 {\n" + "> +\tlcd: lcd at 1 {\n" "> +\t\treg = <1>;\t/* CS1 */\n" "> +\t\tcompatible =\t\"omapdss,tpo,td043mtea1\";\n" "> +\t\tspi-max-frequency = <100000>;\n" @@ -127,4 +115,4 @@ "\n" Tony -fcad45f4fbe247ba32666aa102c7ce1cf5c18d9e32ab62fde9578f8cec280ac9 +aabed7ded1a318b1c9fb40091e3a3c5cd35534eca889d9db06faecd2d4351ea0
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.