Greg Kroah-Hartman
598cf27219
Link: https://lore.kernel.org/r/20260217200002.683975158@linuxfoundation.org Tested-by: Florian Fainelli <florian.fainelli@broadcom.com> Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com> Tested-by: Peter Schneider <pschneider1968@googlemail.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Salvatore Bonaccorso <carnil@debian.org> Tested-by: Brett A C Sheffield <bacs@librecast.net> Tested-by: Mark Brown <broonie@kernel.org> Tested-by: Luna Jernberg <droidbittin@gmail.com> Tested-by: Ronald Warsow <rwarsow@gmx.de> Tested-by: Justin M. Forbes <jforbes@fedoraproject.org> Tested-by: Ron Economos <re@w6rz.net> Tested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
28 lines
883 B
Plaintext
28 lines
883 B
Plaintext
Macronix NANDs Device Tree Bindings
|
|
-----------------------------------
|
|
|
|
Macronix NANDs support randomizer operation for scrambling user data,
|
|
which can be enabled with a SET_FEATURE. The penalty when using the
|
|
randomizer are subpage accesses prohibited and more time period needed
|
|
for program operation, i.e., tPROG 300us to 340us (randomizer enabled).
|
|
Enabling the randomizer is a one time persistent and non reversible
|
|
operation.
|
|
|
|
For more high-reliability concern, if subpage write is not available
|
|
with hardware ECC and not enabled at UBI level, then enabling the
|
|
randomizer is recommended by default by adding a new specific property
|
|
in children nodes.
|
|
|
|
Required NAND chip properties in children mode:
|
|
- randomizer enable: should be "mxic,enable-randomizer-otp"
|
|
|
|
Example:
|
|
|
|
nand: nand-controller@unit-address {
|
|
|
|
nand@0 {
|
|
reg = <0>;
|
|
mxic,enable-randomizer-otp;
|
|
};
|
|
};
|