From: Hui-Ping Chen <hpchen0nvt@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
sumit.semwal@linaro.org, christian.koenig@amd.com,
esben@geanix.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH 1/2] dt-bindings: mtd: nuvoton,ma35d1-nand: add new bindings
Date: Mon, 12 Aug 2024 17:02:56 +0800 [thread overview]
Message-ID: <203578df-11a6-425a-b2be-cc09dae62f8f@gmail.com> (raw)
In-Reply-To: <7a8b9bdf-f4df-4da0-83ca-157175817e99@kernel.org>
Dear Krzysztof,
Thank you for your reply.
On 2024/8/12 下午 02:25, Krzysztof Kozlowski wrote:
> On 12/08/2024 05:00, Hui-Ping Chen wrote:
>> Add dt-bindings for the Nuvoton MA35 SoC NAND Controller.
>>
>> Signed-off-by: Hui-Ping Chen <hpchen0nvt@gmail.com>
>> ---
>> .../bindings/mtd/nuvoton,ma35d1-nand.yaml | 97 +++++++++++++++++++
>> 1 file changed, 97 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/mtd/nuvoton,ma35d1-nand.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/mtd/nuvoton,ma35d1-nand.yaml b/Documentation/devicetree/bindings/mtd/nuvoton,ma35d1-nand.yaml
>> new file mode 100644
>> index 000000000000..988c43bc6e99
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/mtd/nuvoton,ma35d1-nand.yaml
>> @@ -0,0 +1,97 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/mtd/nuvoton,ma35d1-nand.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Nuvoton MA35D1 NAND Flash Interface (NFI) Controller
>> +
>> +allOf:
>> + - $ref: nand-controller.yaml#
> allOf goes usually just before properties.
Okay. I will modify this order.
>> +
>> +maintainers:
>> + - Hui-Ping Chen <hpchen0nvt@gmail.com>
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - nuvoton,ma35d1-nand
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + interrupts:
>> + maxItems: 1
>> +
>> + clocks:
>> + minItems: 1
> This cannot be min only. It's unconstrained. maxItems instead. There is
> no existing code like this so this should make you wonder...
Yes, it should be `maxItems`. I will correct this mistake.
>> +
>> +patternProperties:
>> + "^nand@[a-f0-9]$":
>> + type: object
>> + $ref: raw-nand-chip.yaml
>> + properties:
>> + nand-ecc-mode:
>> + const: hw
> No, drop the property. It does not make sense to have it const.
> Compatible defines it.
Okay. I will remove it.
>> +
>> + nand-ecc-step-size:
>> + enum: [512, 1024]
> No defaults? So is this required?
This is required, but I will also add a default.
>> +
>> + nand-ecc-strength:
>> + enum: [8, 12, 24]
> No defaults? So is this required?
This is required, but I will also add a default.
>> +
>> + nand-bus-width:
>> + const: 8
> Drop property.
Okay. I will remove it.
>> +
>> + unevaluatedProperties: false
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - interrupts
>> + - clocks
>> +
>> +unevaluatedProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>> + #include <dt-bindings/clock/nuvoton,ma35d1-clk.h>
>> +
>> + soc {
>> + #address-cells = <2>;
>> + #size-cells = <2>;
>> +
>> + nand-controller@401A0000 {
>> + compatible = "nuvoton,ma35d1-nand";
>> + reg = <0x0 0x401A0000 0x0 0x1000>;
>> + interrupts = <GIC_SPI 38 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&clk NAND_GATE>;
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + nand@0 {
>> + reg = <0>;
>> +
>> + nand-on-flash-bbt;
>> + nand-ecc-mode = "hw";
> Drop
Okay. I will remove it.
>> + nand-ecc-step-size = <512>;
>> + nand-ecc-strength = <8>;
>> + nand-bus-width = <8>;
> Drop
Okay. I will remove it.
>> +
>> + partitions {
>> + compatible = "fixed-partitions";
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> +
>> + uboot@0 {
>> + label = "nand-uboot";
>> + read-only;
>> + reg = <0x0 0x300000>;
>> + };
>> + };
>> + };
>> + };
>> + };
>> +
>> +...
> Best regards,
> Krzysztof
Best regards,
Hui-Ping Chen
next prev parent reply other threads:[~2024-08-12 9:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 3:00 [PATCH 0/2] Add support for nuvoton ma35 nand controller Hui-Ping Chen
2024-08-12 3:00 ` [PATCH 1/2] dt-bindings: mtd: nuvoton,ma35d1-nand: add new bindings Hui-Ping Chen
2024-08-12 6:25 ` Krzysztof Kozlowski
2024-08-12 9:02 ` Hui-Ping Chen [this message]
2024-08-12 9:12 ` Krzysztof Kozlowski
2024-08-12 9:39 ` Hui-Ping Chen
2024-08-12 3:00 ` [PATCH 2/2] mtd: rawnand: nuvoton: add new driver for the Nuvoton MA35 SoC Hui-Ping Chen
2024-08-12 6:30 ` Krzysztof Kozlowski
2024-08-12 9:10 ` Hui-Ping Chen
2024-08-12 9:13 ` Krzysztof Kozlowski
2024-08-12 9:46 ` Hui-Ping Chen
2024-08-12 12:52 ` kernel test robot
2024-08-13 21:59 ` kernel test robot
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=203578df-11a6-425a-b2be-cc09dae62f8f@gmail.com \
--to=hpchen0nvt@gmail.com \
--cc=christian.koenig@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=esben@geanix.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=sumit.semwal@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).