public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/6] bmips: bcm63268: add support for brcmnand
Date: Wed, 14 Aug 2019 15:23:23 +0200	[thread overview]
Message-ID: <68b7e54c-2ecd-2456-4e68-7d53e0783909@gmail.com> (raw)
In-Reply-To: <20190813191958.14360-6-noltari@gmail.com>



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 <noltari@gmail.com>
> ---
>  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

  reply	other threads:[~2019-08-14 13:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13 19:19 [U-Boot] [PATCH 0/6] bmips: add brcmnand support Álvaro Fernández Rojas
2019-08-13 19:19 ` [U-Boot] [PATCH 1/6] nand: brcm: add BCM6368 support Álvaro Fernández Rojas
2019-08-14 13:18   ` Daniel Schwierzeck
2019-08-13 19:19 ` [U-Boot] [PATCH 2/6] bmips: bcm6368: add support for brcmnand Álvaro Fernández Rojas
2019-08-13 19:19 ` [U-Boot] [PATCH 3/6] bmips: bcm6328: " Álvaro Fernández Rojas
2019-08-13 19:19 ` [U-Boot] [PATCH 4/6] bmips: bcm6362: " Álvaro Fernández Rojas
2019-08-13 19:19 ` [U-Boot] [PATCH 5/6] bmips: bcm63268: " Álvaro Fernández Rojas
2019-08-14 13:23   ` Daniel Schwierzeck [this message]
2019-08-22  9:09     ` Álvaro Fernández Rojas
2019-08-13 19:19 ` [U-Boot] [PATCH 6/6] bmips: enable vr-3032u nand support Álvaro Fernández Rojas
2019-08-28 11:44 ` [U-Boot] [PATCH V2 0/6] bmips: add brcmnand support Álvaro Fernández Rojas
2019-08-28 11:44   ` [U-Boot] [PATCH V2 1/6] nand: brcm: add BCM6368 support Álvaro Fernández Rojas
2019-08-28 13:07     ` Daniel Schwierzeck
2019-08-28 11:44   ` [U-Boot] [PATCH V2 2/6] bmips: bcm6368: add support for brcmnand Álvaro Fernández Rojas
2019-08-28 11:44   ` [U-Boot] [PATCH V2 3/6] bmips: bcm6328: " Álvaro Fernández Rojas
2019-08-28 11:44   ` [U-Boot] [PATCH V2 4/6] bmips: bcm6362: " Álvaro Fernández Rojas
2019-08-28 11:44   ` [U-Boot] [PATCH V2 5/6] bmips: bcm63268: " Álvaro Fernández Rojas
2019-08-28 11:44   ` [U-Boot] [PATCH 6/6] bmips: enable vr-3032u nand support Álvaro Fernández Rojas
2019-08-28 17:12   ` [U-Boot] [PATCH V3 0/6] bmips: add brcmnand support Álvaro Fernández Rojas
2019-08-28 17:12     ` [U-Boot] [PATCH V3 1/6] nand: brcm: add BCM6368 support Álvaro Fernández Rojas
2019-08-28 17:12     ` [U-Boot] [PATCH V3 2/6] bmips: bcm6368: add support for brcmnand Álvaro Fernández Rojas
2019-08-28 17:12     ` [U-Boot] [PATCH V3 3/6] bmips: bcm6328: " Álvaro Fernández Rojas
2019-08-28 17:12     ` [U-Boot] [PATCH V3 4/6] bmips: bcm6362: " Álvaro Fernández Rojas
2019-08-28 17:12     ` [U-Boot] [PATCH V3 5/6] bmips: bcm63268: " Álvaro Fernández Rojas
2019-08-28 17:12     ` [U-Boot] [PATCH V3 6/6] bmips: enable vr-3032u nand support Álvaro Fernández Rojas
2019-10-18 11:05     ` [U-Boot] [PATCH V3 0/6] bmips: add brcmnand support Daniel Schwierzeck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=68b7e54c-2ecd-2456-4e68-7d53e0783909@gmail.com \
    --to=daniel.schwierzeck@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox