From: Michael Walle <michael@walle.cc>
To: Tudor Ambarus <tudor.ambarus@microchip.com>,
Pratyush Yadav <p.yadav@ti.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC v1 2/2] mtd: spi-nor: expose internal parameters via debugfs
Date: Mon, 18 Apr 2022 14:13:28 +0200 [thread overview]
Message-ID: <fca7f401141caee41f574cdd0339a6e1@walle.cc> (raw)
In-Reply-To: <20220418121044.2825448-2-michael@walle.cc>
Am 2022-04-18 14:10, schrieb Michael Walle:
> There is no way to gather all information to verify support for a new
> flash chip. Also if you want to convert an existing flash chip to the
> new SFDP parsing, there is not enough information to determine if the
> flash will work like before. To ease this development, expose internal
> parameters via the debugfs.
Here's an example:
# cat params
name w25q32dw
id ef6016
size 4.00 MiB
write size 1
page size 256
address width 3
flags HAS_SR_TB|HAS_LOCK|HAS_16BIT_SR|NO_READ_CR|SOFT_RESET
opcodes
read 3b
dummy cycles 8
erase 20
program 02
8D extension none
protocols
read 1S-1S-2S
write 1S-1S-1S
register 1S-1S-1S
erase commands
20 (4.00 KiB) [1]
52 (32.0 KiB) [2]
d8 (64.0 KiB) [3]
c7 (4.00 MiB)
sector map
region | erase mask | flags
--------------------+------------+----------
00000000 - 003fffff | [ 123] |
# cat capabilities
Supported read modes by the flash
1S-1S-1S
opcode 03
mode cycles 00
dummy cycles 00
1S-1S-1S (fast read)
opcode 0b
mode cycles 00
dummy cycles 08
1S-1S-2S
opcode 3b
mode cycles 00
dummy cycles 08
1S-2S-2S
opcode bb
mode cycles 02
dummy cycles 02
1S-1S-4S
opcode 6b
mode cycles 00
dummy cycles 08
1S-4S-4S
opcode eb
mode cycles 02
dummy cycles 04
4S-4S-4S
opcode eb
mode cycles 02
dummy cycles 00
Supported page program modes by the flash
1S-1S-1S
opcode 02
WARNING: multiple messages have this Message-ID (diff)
From: Michael Walle <michael@walle.cc>
To: Tudor Ambarus <tudor.ambarus@microchip.com>,
Pratyush Yadav <p.yadav@ti.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC v1 2/2] mtd: spi-nor: expose internal parameters via debugfs
Date: Mon, 18 Apr 2022 14:13:28 +0200 [thread overview]
Message-ID: <fca7f401141caee41f574cdd0339a6e1@walle.cc> (raw)
In-Reply-To: <20220418121044.2825448-2-michael@walle.cc>
Am 2022-04-18 14:10, schrieb Michael Walle:
> There is no way to gather all information to verify support for a new
> flash chip. Also if you want to convert an existing flash chip to the
> new SFDP parsing, there is not enough information to determine if the
> flash will work like before. To ease this development, expose internal
> parameters via the debugfs.
Here's an example:
# cat params
name w25q32dw
id ef6016
size 4.00 MiB
write size 1
page size 256
address width 3
flags HAS_SR_TB|HAS_LOCK|HAS_16BIT_SR|NO_READ_CR|SOFT_RESET
opcodes
read 3b
dummy cycles 8
erase 20
program 02
8D extension none
protocols
read 1S-1S-2S
write 1S-1S-1S
register 1S-1S-1S
erase commands
20 (4.00 KiB) [1]
52 (32.0 KiB) [2]
d8 (64.0 KiB) [3]
c7 (4.00 MiB)
sector map
region | erase mask | flags
--------------------+------------+----------
00000000 - 003fffff | [ 123] |
# cat capabilities
Supported read modes by the flash
1S-1S-1S
opcode 03
mode cycles 00
dummy cycles 00
1S-1S-1S (fast read)
opcode 0b
mode cycles 00
dummy cycles 08
1S-1S-2S
opcode 3b
mode cycles 00
dummy cycles 08
1S-2S-2S
opcode bb
mode cycles 02
dummy cycles 02
1S-1S-4S
opcode 6b
mode cycles 00
dummy cycles 08
1S-4S-4S
opcode eb
mode cycles 02
dummy cycles 04
4S-4S-4S
opcode eb
mode cycles 02
dummy cycles 00
Supported page program modes by the flash
1S-1S-1S
opcode 02
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-04-18 12:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 12:10 [PATCH RFC v1 1/2] mtd: spi-nor: export spi_nor_hwcaps_pp2cmd() Michael Walle
2022-04-18 12:10 ` Michael Walle
2022-04-18 12:10 ` [PATCH RFC v1 2/2] mtd: spi-nor: expose internal parameters via debugfs Michael Walle
2022-04-18 12:10 ` Michael Walle
2022-04-18 12:13 ` Michael Walle [this message]
2022-04-18 12:13 ` Michael Walle
2022-04-20 5:23 ` Pratyush Yadav
2022-04-20 5:23 ` Pratyush Yadav
2022-04-20 9:18 ` Michael Walle
2022-04-20 9:18 ` Michael Walle
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=fca7f401141caee41f574cdd0339a6e1@walle.cc \
--to=michael@walle.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.