From: William Zhang <william.zhang@broadcom.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
David Regan <dregan@broadcom.com>
Cc: dregan@mail.com, richard@nod.at, vigneshr@ti.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, computersforpeace@gmail.com,
kdasu.kdev@gmail.com, linux-mtd@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
joel.peshkin@broadcom.com, tomer.yacoby@broadcom.com,
dan.beygelman@broadcom.com, anand.gore@broadcom.com,
kursad.oney@broadcom.com, florian.fainelli@broadcom.com,
rafal@milecki.pl, bcm-kernel-feedback-list@broadcom.com,
andre.przywara@arm.com, baruch@tkos.co.il,
linux-arm-kernel@lists.infradead.org, dan.carpenter@linaro.org
Subject: Re: [PATCH v3 02/10] ARM: dts: broadcom: bcmbca: Add NAND controller node
Date: Wed, 24 Jan 2024 19:09:23 -0800 [thread overview]
Message-ID: <2c10a764-f74f-45b2-8bba-77c40468f4b5@broadcom.com> (raw)
In-Reply-To: <20240124183008.04a1bcb0@xps-13>
[-- Attachment #1.1: Type: text/plain, Size: 3219 bytes --]
Hi Miquel,
On 1/24/24 09:30, Miquel Raynal wrote:
> Hi David,
>
> dregan@broadcom.com wrote on Tue, 23 Jan 2024 19:04:50 -0800:
>
>> From: William Zhang <william.zhang@broadcom.com>
>>
>> Add support for Broadcom STB NAND controller in BCMBCA ARMv7 chip dts
>> files.
>>
>> Signed-off-by: William Zhang <william.zhang@broadcom.com>
>> Reviewed-by: David Regan <dregan@broadcom.com>
>> ---
>> Changes in v3: None
>> ---
>> Changes in v2: None
>> ---
>> arch/arm/boot/dts/broadcom/bcm47622.dtsi | 17 +++++++++++++++++
>> arch/arm/boot/dts/broadcom/bcm63138.dtsi | 10 +++++++++-
>> arch/arm/boot/dts/broadcom/bcm63148.dtsi | 17 +++++++++++++++++
>> arch/arm/boot/dts/broadcom/bcm63178.dtsi | 17 +++++++++++++++++
>> arch/arm/boot/dts/broadcom/bcm6756.dtsi | 17 +++++++++++++++++
>> arch/arm/boot/dts/broadcom/bcm6846.dtsi | 17 +++++++++++++++++
>> arch/arm/boot/dts/broadcom/bcm6855.dtsi | 17 +++++++++++++++++
>> arch/arm/boot/dts/broadcom/bcm6878.dtsi | 17 +++++++++++++++++
>> arch/arm/boot/dts/broadcom/bcm947622.dts | 4 ++++
>> arch/arm/boot/dts/broadcom/bcm963138.dts | 4 ++++
>> arch/arm/boot/dts/broadcom/bcm963138dvt.dts | 12 +++++-------
>> arch/arm/boot/dts/broadcom/bcm963148.dts | 4 ++++
>> arch/arm/boot/dts/broadcom/bcm963178.dts | 4 ++++
>> arch/arm/boot/dts/broadcom/bcm96756.dts | 4 ++++
>> arch/arm/boot/dts/broadcom/bcm96846.dts | 4 ++++
>> arch/arm/boot/dts/broadcom/bcm96855.dts | 4 ++++
>> arch/arm/boot/dts/broadcom/bcm96878.dts | 4 ++++
>> 17 files changed, 165 insertions(+), 8 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/broadcom/bcm47622.dtsi b/arch/arm/boot/dts/broadcom/bcm47622.dtsi
>> index 7cd38de118c3..55ff18043d96 100644
>> --- a/arch/arm/boot/dts/broadcom/bcm47622.dtsi
>> +++ b/arch/arm/boot/dts/broadcom/bcm47622.dtsi
>> @@ -138,6 +138,23 @@ hsspi: spi@1000 {
>> status = "disabled";
>> };
>>
>> + nand_controller: nand-controller@1800 {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + compatible = "brcm,nand-bcm63138", "brcm,brcmnand-v7.1", "brcm,brcmnand";
>> + reg = <0x1800 0x600>, <0x2000 0x10>;
>> + reg-names = "nand", "nand-int-base";
>> + brcm,nand-use-wp = <0>;
>> + status = "disabled";
>> +
>> + nandcs: nand@0 {
>> + compatible = "brcm,nandcs";
>> + reg = <0>;
>> + nand-on-flash-bbt;
>> + brcm,nand-ecc-use-strap;
>
> Describing the NAND chip in a SoC DTSI does not look relevant to me.
> Even more if you add something like this nand-ecc-use-strap setting
> which is very board dependent.
>
I am not sure if I understand you comments correctly but are you
suggesting to put this whole nand controller node into each board dts?
We have other ip block nodes like SPI, uart in this same soc dtsi file
too. For all the bcmbca soc dtsi I am updating here(and its board
design), we always use the strap to for ecc setting. So I thought it
should be okay to put brcm,nand-ecc-use-strap in the default dtsi file.
For any board that uses the raw nand nand-ecc property, the board dts
can do so and override the brcm,nand-ecc-use-strap setting.
> Same applies to your arm64 DT patch.
>
> Thanks,
> Miquèl
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4212 bytes --]
[-- Attachment #2: Type: text/plain, Size: 144 bytes --]
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2024-01-25 3:09 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 3:04 [PATCH v3 00/10] mtd: rawnand: brcmnand: driver and doc updates David Regan
2024-01-24 3:04 ` [PATCH v3 01/10] dt-bindings: mtd: brcmnand: Updates for bcmbca SoCs David Regan
2024-01-24 17:24 ` Conor Dooley
2024-01-25 3:01 ` William Zhang
2024-01-25 19:51 ` Conor Dooley
2024-01-26 1:55 ` William Zhang
2024-01-26 16:46 ` Conor Dooley
2024-01-26 18:09 ` William Zhang
2024-01-24 17:24 ` Conor Dooley
2024-01-24 17:34 ` Miquel Raynal
2024-01-25 3:14 ` William Zhang
2024-01-24 3:04 ` [PATCH v3 02/10] ARM: dts: broadcom: bcmbca: Add NAND controller node David Regan
2024-01-24 17:30 ` Miquel Raynal
2024-01-25 3:09 ` William Zhang [this message]
2024-01-25 3:34 ` Florian Fainelli
2024-01-25 5:53 ` William Zhang
2024-01-25 9:20 ` Miquel Raynal
2024-01-25 18:14 ` William Zhang
2024-01-24 3:04 ` [PATCH v3 03/10] arm64: " David Regan
2024-01-24 3:04 ` [PATCH v3 04/10] mtd: rawnand: brcmnand: Rename bcm63138 nand driver David Regan
2024-01-24 3:04 ` [PATCH v3 05/10] mtd: rawnand: brcmnand: Add BCMBCA read data bus interface David Regan
2024-01-24 3:04 ` [PATCH v3 06/10] mtd: rawnand: brcmnand: Add support for getting ecc setting from strap David Regan
2024-01-24 17:32 ` Miquel Raynal
2024-01-25 3:13 ` William Zhang
2024-01-24 3:04 ` [PATCH v3 07/10] mtd: rawnand: brcmnand: Support write protection setting from dts David Regan
2024-01-24 3:04 ` [PATCH v3 08/10] mtd: rawnand: brcmnand: exec_op helper functions return type fixes David Regan
2024-01-24 17:35 ` Miquel Raynal
2024-01-24 3:04 ` [PATCH v3 09/10] mtd: rawnand: brcmnand: update log level messages David Regan
2024-01-24 17:37 ` Miquel Raynal
2024-01-25 18:47 ` David Regan
2024-01-24 3:04 ` [PATCH v3 10/10] mtd: rawnand: brcmnand: allow for on-die ecc David Regan
2024-01-24 17:40 ` Miquel Raynal
2024-01-25 19:47 ` David Regan
2024-01-26 6:19 ` Miquel Raynal
2024-01-26 19:57 ` David Regan
2024-01-29 10:52 ` Miquel Raynal
2024-01-30 8:11 ` William Zhang
2024-01-30 11:01 ` Miquel Raynal
2024-01-30 15:26 ` David Regan
2024-01-30 18:55 ` Miquel Raynal
2024-02-01 6:48 ` William Zhang
2024-02-01 8:25 ` Miquel Raynal
2024-02-01 18:53 ` William Zhang
2024-02-02 17:38 ` David Regan
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=2c10a764-f74f-45b2-8bba-77c40468f4b5@broadcom.com \
--to=william.zhang@broadcom.com \
--cc=anand.gore@broadcom.com \
--cc=andre.przywara@arm.com \
--cc=baruch@tkos.co.il \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=conor+dt@kernel.org \
--cc=dan.beygelman@broadcom.com \
--cc=dan.carpenter@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dregan@broadcom.com \
--cc=dregan@mail.com \
--cc=florian.fainelli@broadcom.com \
--cc=joel.peshkin@broadcom.com \
--cc=kdasu.kdev@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=rafal@milecki.pl \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=tomer.yacoby@broadcom.com \
--cc=vigneshr@ti.com \
/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