From: Rob Herring <robh@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Cheng Ming Lin <linchengming884@gmail.com>,
richard@nod.at, vigneshr@ti.com, krzk+dt@kernel.org,
conor+dt@kernel.org, tudor.ambarus@linaro.org,
mmkurbanov@salutedevices.com, Takahiro.Kuwano@infineon.com,
pratyush@kernel.org, linux-mtd@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
alvinzhou@mxic.com.tw, Cheng Ming Lin <chengminglin@mxic.com.tw>
Subject: Re: [PATCH v2 1/3] dt-bindings: mtd: spi-nand: Add enable-randomizer-otp property
Date: Wed, 10 Sep 2025 11:36:31 -0500 [thread overview]
Message-ID: <20250910163631.GA142639-robh@kernel.org> (raw)
In-Reply-To: <87wm66d67k.fsf@bootlin.com>
On Wed, Sep 10, 2025 at 11:09:35AM +0200, Miquel Raynal wrote:
> Hello Cheng Ming,
>
> On 10/09/2025 at 11:02:59 +08, Cheng Ming Lin <linchengming884@gmail.com> wrote:
>
> > From: Cheng Ming Lin <chengminglin@mxic.com.tw>
> >
> > Add a new boolean property "enable-randomizer-otp" to enable the
> > randomizer feature on supported SPI-NAND devices.
> >
> > Signed-off-by: Cheng Ming Lin <chengminglin@mxic.com.tw>
> > ---
> > Documentation/devicetree/bindings/mtd/spi-nand.yaml | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/mtd/spi-nand.yaml b/Documentation/devicetree/bindings/mtd/spi-nand.yaml
> > index 77a8727c7..432bc79e9 100644
> > --- a/Documentation/devicetree/bindings/mtd/spi-nand.yaml
> > +++ b/Documentation/devicetree/bindings/mtd/spi-nand.yaml
> > @@ -21,6 +21,10 @@ properties:
> > description: Encode the chip-select line on the SPI bus
> > maxItems: 1
> >
> > + enable-randomizer-otp:
>
> This is a NAND wide feature, so we should probably add a prefix, such as
> "nand,".
'nand' is not a vendor, so no.
Rob
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2025-09-10 16:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 3:02 [PATCH v2 0/3] mtd: spi-nand: Add support for randomizer Cheng Ming Lin
2025-09-10 3:02 ` [PATCH v2 1/3] dt-bindings: mtd: spi-nand: Add enable-randomizer-otp property Cheng Ming Lin
2025-09-10 9:09 ` Miquel Raynal
2025-09-10 16:36 ` Rob Herring [this message]
2025-09-11 7:08 ` Miquel Raynal
2025-09-11 7:24 ` Cheng Ming Lin
2025-09-11 7:59 ` Miquel Raynal
2025-09-11 8:30 ` Cheng Ming Lin
2025-09-11 13:56 ` Miquel Raynal
2025-09-12 7:50 ` Cheng Ming Lin
2025-09-10 11:40 ` Krzysztof Kozlowski
2025-09-11 8:05 ` Cheng Ming Lin
2025-09-10 3:03 ` [PATCH v2 2/3] mtd: spi-nand: Add support for randomizer Cheng Ming Lin
2025-09-10 3:03 ` [PATCH v2 3/3] mtd: spi-nand: macronix: Add randomizer support Cheng Ming Lin
2025-09-10 9:12 ` Miquel Raynal
2025-09-10 9:26 ` Cheng Ming Lin
2025-09-10 9:43 ` Miquel Raynal
2025-09-11 5:15 ` Cheng Ming Lin
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=20250910163631.GA142639-robh@kernel.org \
--to=robh@kernel.org \
--cc=Takahiro.Kuwano@infineon.com \
--cc=alvinzhou@mxic.com.tw \
--cc=chengminglin@mxic.com.tw \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linchengming884@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mmkurbanov@salutedevices.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=tudor.ambarus@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