public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Akhila YS <akhilayalmati@gmail.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mtd: hisilicon,504-nfc: convert to DT schema
Date: Thu, 12 Mar 2026 10:28:51 -0500	[thread overview]
Message-ID: <20260312152851.GA3190071-robh@kernel.org> (raw)
In-Reply-To: <20260307-hisi504-1-v1-1-8bf9a186faf2@gmail.com>

On Sat, Mar 07, 2026 at 04:43:56PM +0000, Akhila YS wrote:
> Convert Hisilicon Hip04 Soc NAND controller DT binding to YAML format.
> 
> Signed-off-by: Akhila YS <akhilayalmati@gmail.com>
> ---
>  .../devicetree/bindings/mtd/hisilicon,504-nfc.yaml | 90 ++++++++++++++++++++++
>  1 file changed, 90 insertions(+)

Convert implies the removal of the .txt binding. Where is that? Could be 
missing? If so, say that.

> 
> diff --git a/Documentation/devicetree/bindings/mtd/hisilicon,504-nfc.yaml b/Documentation/devicetree/bindings/mtd/hisilicon,504-nfc.yaml
> new file mode 100644
> index 000000000000..805ef0af0e04
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mtd/hisilicon,504-nfc.yaml
> @@ -0,0 +1,90 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mtd/hisilicon,504-nfc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: HiSilicon Hip04 NAND Flash Controller
> +
> +maintainers:
> +  - Miquel Raynal <miquel.raynal@bootlin.com>
> +  - Richard Weinberger <richard@nod.at>

This should be someone with the h/w. I would use the HiSilicon 
maintainer from MAINTAINERS.

> +
> +description:
> +  The HiSilicon 504 NFC is a NAND flash memory controller used in the
> +  Hip04 SoC. It supports hardware ECC for NAND devices and provides
> +  register and buffer regions for NAND operations.
> +
> +allOf:
> +  - $ref: nand-controller.yaml#
> +
> +properties:
> +  compatible:
> +    const: hisilicon,504-nfc
> +
> +  reg:
> +    minItems: 2
> +    maxItems: 2

Need to define what each entry is.

> +
> +  interrupts:
> +    maxItems: 1
> +
> +  nand-bus-width:
> +    enum: [8, 16]
> +
> +  nand-ecc-mode:
> +    enum:
> +      - none
> +      - hw
> +
> +  nand-ecc-strength:
> +    const: 16
> +
> +  nand-ecc-step-size:
> +    const: 1024
> +

> +  "#address-cells":
> +    const: 1
> +
> +  "#size-cells":
> +    const: 0

These can be dropped as the child (partitions) doesn't have an address.

> +
> +  partitions:
> +    $ref: /schemas/mtd/partitions/fixed-partitions.yaml#
> +
> +required:
> +  - compatible
> +  - reg
> +  - interrupts
> +  - nand-bus-width
> +  - nand-ecc-mode
> +  - "#address-cells"
> +  - "#size-cells"
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    nand-controller@4020000 {
> +        compatible = "hisilicon,504-nfc";
> +        reg = <0x04020000 0x10000>, <0x05000000 0x1000>;
> +        interrupts = <0 379 4>;
> +        nand-bus-width = <8>;
> +        nand-ecc-mode = "hw";
> +        nand-ecc-strength = <16>;
> +        nand-ecc-step-size = <1024>;
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        partitions {
> +             compatible = "fixed-partitions";
> +             #address-cells = <1>;
> +             #size-cells = <1>;
> +
> +             partition@0 {
> +                 label = "nand_text";
> +                 reg = <0x0 0x400000>;
> +            };
> +        };
> +    };
> +...
> 
> ---
> base-commit: d4906ae14a5f136ceb671bb14cedbf13fa560da6
> change-id: 20260306-hisi504-1-d7aa09c70d93
> 
> Best regards,
> -- 
> Akhila YS <akhilayalmati@gmail.com>
> 

  reply	other threads:[~2026-03-12 15:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07 16:43 [PATCH] dt-bindings: mtd: hisilicon,504-nfc: convert to DT schema Akhila YS
2026-03-12 15:28 ` Rob Herring [this message]
2026-03-13  6:18   ` Akhila YS
2026-03-13  8:55   ` Miquel Raynal
2026-03-13  8:57     ` Miquel Raynal
2026-03-13 11:55       ` Akhila YS

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=20260312152851.GA3190071-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=akhilayalmati@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --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