From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from proxima.lp0.eu ([2001:8b0:ffea:0:205:b4ff:fe12:530]) by bombadil.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1a0cvt-0007bl-6Q for linux-mtd@lists.infradead.org; Sun, 22 Nov 2015 22:16:30 +0000 Subject: [PATCH (v4) 1/2] mtd: brcmnand: Add brcm,bcm63268-nand device tree binding To: Rob Herring References: <56506D55.3000907@simon.arlott.org.uk> <20151122215945.GA5930@rob-hp-laptop> Cc: "devicetree@vger.kernel.org" , Brian Norris , Linux Kernel Mailing List , David Woodhouse , linux-mtd@lists.infradead.org, Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Florian Fainelli , Jonas Gorski From: Simon Arlott Message-ID: <56523E85.905@simon.arlott.org.uk> Date: Sun, 22 Nov 2015 22:15:33 +0000 MIME-Version: 1.0 In-Reply-To: <20151122215945.GA5930@rob-hp-laptop> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Add device tree binding for NAND on the BCM63268. The BCM63268 has a NAND interrupt register with combined status and enable registers. Signed-off-by: Simon Arlott --- On 22/11/15 21:59, Rob Herring wrote: >> + * "brcm,nand-bcm63268" >> + - compatible: should contain "brcm,nand-bcm", "brcm,nand-bcm63268" > > vendor,-device is preferred. The existing two bindings use brcm,nand-, but I've changed this one. .../devicetree/bindings/mtd/brcm,brcmnand.txt | 33 ++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt b/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt index 4ff7128..2644d6c 100644 --- a/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt +++ b/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt @@ -72,6 +72,13 @@ we define additional 'compatible' properties and associated register resources w and enable registers - reg-names: (required) "nand-int-base" + * "brcm,bcm63268-nand" + - compatible: should contain "brcm,bcm-nand", "brcm,bcm63268-nand" + - reg: (required) the 'NAND_INTR_BASE' register range, with combined status + and enable registers, and boot address registers + - reg-names: (required) "nand-intr-base" + - clock: (required) reference to the clock for NAND controller + * "brcm,nand-iproc" - reg: (required) the "IDM" register range, for interrupt enable and APB bus access endianness configuration, and the "EXT" register range, @@ -148,3 +155,29 @@ nand@f0442800 { }; }; }; + +nand@0x10000200 { + compatible = "brcm,bcm63168-nand", "brcm,bcm63268-nand", + "brcm,brcmnand-v4.0", "brcm,brcmnand"; + reg = <0x10000200 0x180>, + <0x10000600 0x200>, + <0x100000b0 0x10>; + reg-names = "nand", "nand-cache", "nand-intr-base"; + interrupt-parent = <&periph_intc>; + interrupts = <50>; + clocks = <&periph_clk 20>; + + #address-cells = <1>; + #size-cells = <0>; + + nand0: nandcs@0 { + compatible = "brcm,nandcs"; + reg = <0>; + nand-on-flash-bbt; + nand-ecc-strength = <1>; + nand-ecc-step-size = <512>; + + #address-cells = <0>; + #size-cells = <0>; + }; +}; -- 2.1.4 -- Simon Arlott From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Arlott Subject: [PATCH (v4) 1/2] mtd: brcmnand: Add brcm,bcm63268-nand device tree binding Date: Sun, 22 Nov 2015 22:15:33 +0000 Message-ID: <56523E85.905@simon.arlott.org.uk> References: <56506D55.3000907@simon.arlott.org.uk> <20151122215945.GA5930@rob-hp-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20151122215945.GA5930@rob-hp-laptop> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Rob Herring Cc: "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Brian Norris , Linux Kernel Mailing List , David Woodhouse , linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Florian Fainelli , Jonas Gorski List-Id: devicetree@vger.kernel.org Add device tree binding for NAND on the BCM63268. The BCM63268 has a NAND interrupt register with combined status and enable registers. Signed-off-by: Simon Arlott --- On 22/11/15 21:59, Rob Herring wrote: >> + * "brcm,nand-bcm63268" >> + - compatible: should contain "brcm,nand-bcm", "brcm,nand-bcm63268" > > vendor,-device is preferred. The existing two bindings use brcm,nand-, but I've changed this one. .../devicetree/bindings/mtd/brcm,brcmnand.txt | 33 ++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt b/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt index 4ff7128..2644d6c 100644 --- a/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt +++ b/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt @@ -72,6 +72,13 @@ we define additional 'compatible' properties and associated register resources w and enable registers - reg-names: (required) "nand-int-base" + * "brcm,bcm63268-nand" + - compatible: should contain "brcm,bcm-nand", "brcm,bcm63268-nand" + - reg: (required) the 'NAND_INTR_BASE' register range, with combined status + and enable registers, and boot address registers + - reg-names: (required) "nand-intr-base" + - clock: (required) reference to the clock for NAND controller + * "brcm,nand-iproc" - reg: (required) the "IDM" register range, for interrupt enable and APB bus access endianness configuration, and the "EXT" register range, @@ -148,3 +155,29 @@ nand@f0442800 { }; }; }; + +nand@0x10000200 { + compatible = "brcm,bcm63168-nand", "brcm,bcm63268-nand", + "brcm,brcmnand-v4.0", "brcm,brcmnand"; + reg = <0x10000200 0x180>, + <0x10000600 0x200>, + <0x100000b0 0x10>; + reg-names = "nand", "nand-cache", "nand-intr-base"; + interrupt-parent = <&periph_intc>; + interrupts = <50>; + clocks = <&periph_clk 20>; + + #address-cells = <1>; + #size-cells = <0>; + + nand0: nandcs@0 { + compatible = "brcm,nandcs"; + reg = <0>; + nand-on-flash-bbt; + nand-ecc-strength = <1>; + nand-ecc-step-size = <512>; + + #address-cells = <0>; + #size-cells = <0>; + }; +}; -- 2.1.4 -- Simon Arlott -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html