From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Schwierzeck Date: Wed, 14 Aug 2019 15:23:23 +0200 Subject: [U-Boot] [PATCH 5/6] bmips: bcm63268: add support for brcmnand In-Reply-To: <20190813191958.14360-6-noltari@gmail.com> References: <20190813191958.14360-1-noltari@gmail.com> <20190813191958.14360-6-noltari@gmail.com> Message-ID: <68b7e54c-2ecd-2456-4e68-7d53e0783909@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: u-boot@lists.denx.de Am 13.08.19 um 21:19 schrieb Álvaro Fernández Rojas: > BCM63268 uses 4.0 HW nand controller, which is currently supported by > brcmnand driver. > > Signed-off-by: Álvaro Fernández Rojas > --- > arch/mips/dts/brcm,bcm63268.dtsi | 18 ++++++++++++++++++ > 1 file changed, 18 insertions(+) > > diff --git a/arch/mips/dts/brcm,bcm63268.dtsi b/arch/mips/dts/brcm,bcm63268.dtsi > index f8a72ef535..5294242529 100644 > --- a/arch/mips/dts/brcm,bcm63268.dtsi > +++ b/arch/mips/dts/brcm,bcm63268.dtsi > @@ -141,6 +141,24 @@ > status = "disabled"; > }; > > + nand: nand-controller at 10000200 { > + #address-cells = <1>; > + #size-cells = <0>; > + compatible = "brcm,nand-bcm6368", if BCM63268 is already supported by brcmnand, why should it match with your new driver? > + "brcm,brcmnand-v4.0", > + "brcm,brcmnand"; > + reg-names = "nand", > + "nand-cache", > + "nand-int-base"; > + reg = <0x10000200 0x180>, > + <0x10000600 0x200>, > + <0x100000b0 0x10>; > + clocks = <&periph_clk BCM63268_CLK_NAND>; > + clock-names = "nand"; > + > + status = "disabled"; > + }; > + > periph_pwr: power-controller at 1000184c { > compatible = "brcm,bcm6328-power-domain"; > reg = <0x1000184c 0x4>; > -- - Daniel