]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
mtd: spi-nor: Add steps for testing locking support
authorMiquel Raynal <miquel.raynal@bootlin.com>
Tue, 26 May 2026 14:56:44 +0000 (16:56 +0200)
committerPratyush Yadav <pratyush@kernel.org>
Wed, 27 May 2026 12:36:02 +0000 (14:36 +0200)
commit6000eab4515a2a381557a48c35e248a3418f2bc6
tree612f1c8cb6c5db5ece28d8c8d36e96a4ca34d5fb
parentf05f0d62c5c6b981315bd10017ec98504165e355
mtd: spi-nor: Add steps for testing locking support

As recently raised on the mailing list, it may be useful to propose a
list of steps to go through in order to prove the devices have been
described correctly, especially since all the block protection
information is not stored in any kind of table and is instead filled
manually by developers.

Use the debugfs output to ease the comparison between expectations and
reality.

[rdunlap@infradead.org: fix build warning]
Link: https://lore.kernel.org/linux-mtd/20260526172341.773398-1-rdunlap@infradead.org/
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Pratyush Yadav <pratyush@kernel.org>
Documentation/driver-api/mtd/spi-nor.rst