From: Cheng Ming Lin <linchengming884@gmail.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Tudor Ambarus <tudor.ambarus@linaro.org>,
Mikhail Kshevetskiy <mikhail.kshevetskiy@iopsys.eu>,
Pablo Martin-Gomez <pmartin-gomez@freebox.fr>,
Tianling Shen <cnsztl@gmail.com>,
Pratyush Yadav <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: [PATCH v6 0/3] mtd: spi-nand: Add support for randomizer feature
Date: Mon, 23 Feb 2026 14:17:03 +0800 [thread overview]
Message-ID: <20260223061706.1027986-1-linchengming884@gmail.com> (raw)
From: Cheng Ming Lin <chengminglin@mxic.com.tw>
This patch series introduces randomizer support for SPI NAND devices.
- Patch 1: add the nand-randomizer-enable and nand-randomizer-disable
boolean properties to the generic nand-chip.yaml bindings.
- Patch 2: add the initialization logic and the set_randomizer callback
to the core framework. The core will now parse the device tree
properties and enable or disable the randomizer accordingly
during spinand_init.
- Patch 3: implement the set_randomizer callback specifically for Macronix
chips (MX35LF/UF series) to handle the vendor-specific register
operations.
v6:
* Added mutual-exclusive constraints using not with required for
nand-randomizer-enable and nand-randomizer-disable properties based
on Krzysztof's feedback.
* Simplified the return path in macronix_set_randomizer() to directly
return ret; and dropped unrelated formatting changes.
v5:
* Promoted the randomizer configuration to use generic NAND properties
(nand-randomizer-enable and nand-randomizer-disable) instead of
vendor-specific bindings.
* Refactored the initialization architecture in core.c. The core framework
is now responsible for parsing the device tree properties and deciding
whether to enable or disable the randomizer.
v4:
* Fix a build error in spinand_randomizer_init() where a value was
returned from a void function. (Reported by kernel test robot)
* Update the return type to int.
v3:
* Revert the device tree property to the vendor-specific
"mxic,randomizer-enable" to strictly follow vendor-specific bindings.
* Update the 'set_randomizer' callback signature to accept a boolean
'enable' argument, allowing the feature to be explicitly enabled or
disabled.
* Switch the implementation to use the standard SET_FEATURE command
to modify the Configuration Register (0x10), replacing the previous
special program command method.
v2:
* Create a global NAND DT property
Cheng Ming Lin (3):
dt-bindings: mtd: spinand: Add randomizer enable/disable properties
mtd: spi-nand: Add support for randomizer
mtd: spi-nand: macronix: Enable randomizer support
.../devicetree/bindings/mtd/nand-chip.yaml | 18 ++++++++
drivers/mtd/nand/spi/core.c | 27 ++++++++++++
drivers/mtd/nand/spi/macronix.c | 42 ++++++++++++++-----
include/linux/mtd/spinand.h | 9 ++++
4 files changed, 86 insertions(+), 10 deletions(-)
--
2.25.1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2026-02-23 6:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 6:17 Cheng Ming Lin [this message]
2026-02-23 6:17 ` [PATCH v6 1/3] dt-bindings: mtd: spinand: Add randomizer enable/disable properties Cheng Ming Lin
2026-02-23 6:17 ` [PATCH v6 2/3] mtd: spi-nand: Add support for randomizer Cheng Ming Lin
2026-02-23 6:17 ` [PATCH v6 3/3] mtd: spi-nand: macronix: Enable randomizer support 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=20260223061706.1027986-1-linchengming884@gmail.com \
--to=linchengming884@gmail.com \
--cc=alvinzhou@mxic.com.tw \
--cc=chengminglin@mxic.com.tw \
--cc=cnsztl@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=mikhail.kshevetskiy@iopsys.eu \
--cc=miquel.raynal@bootlin.com \
--cc=pmartin-gomez@freebox.fr \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--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