| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <5282552B.4000801@ti.com>
Date: Tue, 12 Nov 2013 11:19:55 -0500
From: Santosh Shilimkar <santosh.shilimkar@...com>
To: "Khoronzhuk, Ivan" <ivan.khoronzhuk@...com>
CC: Rob Landley <rob@...dley.net>,
Russell King <linux@....linux.org.uk>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Rob Herring <rob.herring@...xeda.com>,
Stephen Warren <swarren@...dotorg.org>,
Kumar Gala <galak@...nel.crashing.org>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
"Strashko, Grygorii" <grygorii.strashko@...com>
Subject: Re: [PATCH 12/12] arm: dts: keystone: add AEMIF/NAND device entry
On Monday 11 November 2013 12:13 PM, Khoronzhuk, Ivan wrote:
> Add AEMIF/NAND device entry.
>
> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@...com>
> ---
> arch/arm/boot/dts/keystone.dts | 63 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 63 insertions(+)
>
> diff --git a/arch/arm/boot/dts/keystone.dts b/arch/arm/boot/dts/keystone.dts
> index 100bdf5..998da98 100644
> --- a/arch/arm/boot/dts/keystone.dts
> +++ b/arch/arm/boot/dts/keystone.dts
> @@ -179,5 +179,68 @@
> interrupts = <GIC_SPI 300 IRQ_TYPE_EDGE_RISING>;
> clocks = <&clkspi>;
> };
> +
> + aemif@...000A00 {
> + compatible = "ti,keystone-aemif";
> + #address-cells = <2>;
> + #size-cells = <1>;
> + clocks = <&clkaemif>;
> + clock-names = "aemif";
> + clock-ranges;
> +
> + reg = <0x2100A00 0x00000100>;
> + ranges = <0 0 0x30000000 0x10000000
> + 1 0 0x21000A00 0x00000100>;
> +
> + nand:cs0 {
> + compatible = "ti,davinci-cs";
> + #address-cells = <2>;
> + #size-cells = <1>;
> + clock-ranges;
> + ranges;
> +
> + /* all timings in nanoseconds */
> + ti,davinci-cs-ta = <12>;
> + ti,davinci-cs-rhold = <6>;
> + ti,davinci-cs-rstrobe = <23>;
> + ti,davinci-cs-rsetup = <9>;
> + ti,davinci-cs-whold = <8>;
> + ti,davinci-cs-wstrobe = <23>;
> + ti,davinci-cs-wsetup = <8>;
> +
> + nand@0,0 {
> + compatible = "ti,keystone-nand";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + reg = <0 0 0x4000000
> + 1 0 0x0000100>;
> +
> + ti,davinci-chipselect = <0>;
> + ti,davinci-mask-ale = <0x2000>;
> + ti,davinci-mask-cle = <0x4000>;
> + ti,davinci-mask-chipsel = <0>;
> + nand-ecc-mode = "hw";
> + ti,davinci-ecc-bits = <4>;
> + nand-on-flash-bbt;
> +
> + partition@0 {
> + label = "u-boot";
> + reg = <0x0 0x100000>;
> + read-only;
> + };
> +
> + partition@...000 {
> + label = "params";
> + reg = <0x100000 0x80000>;
> + read-only;
> + };
> +
> + partition@...000 {
> + label = "ubifs";
> + reg = <0x180000 0x7E80000>;
> + };
Lets create now board specific k2hk-evm.dts and rename keystone.dts
to keystone.dtsi and include that in boards. That way you can add the
board specific stuff in board files and common soc stuff in keystone.dtsi.
You can update that once the bindings are blessed by DT folks.
Regards,
Santosh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists