From: Krzysztof Kozlowski <krzk@kernel.org>
To: Hui-Ping Chen <hpchen0nvt@gmail.com>,
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 11:12:19 +0200 [thread overview]
Message-ID: <1f823600-68c4-418f-b2bf-6d5d64a1ee56@kernel.org> (raw)
In-Reply-To: <203578df-11a6-425a-b2be-cc09dae62f8f@gmail.com>
On 12/08/2024 11:02, Hui-Ping Chen wrote:
>
>
>>> +
>>> + nand-ecc-step-size:
>>> + enum: [512, 1024]
>> No defaults? So is this required?
>
> This is required, but I will also add a default.
If this is required and should be in required: list. Default does not
make sense then... it contradicts the point of being required.
>
>
>
>>> +
>>> + nand-ecc-strength:
>>> + enum: [8, 12, 24]
>> No defaults? So is this required?
>
> This is required, but I will also add a default.
Ditto
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-12 9:12 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
2024-08-12 9:12 ` Krzysztof Kozlowski [this message]
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=1f823600-68c4-418f-b2bf-6d5d64a1ee56@kernel.org \
--to=krzk@kernel.org \
--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=hpchen0nvt@gmail.com \
--cc=krzk+dt@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