From: Harry Chou <harryyc.chou@gmail.com>
To: cyrille.pitchen@wedev4u.fr
Cc: dwmw2@infradead.org, computersforpeace@gmail.com,
boris.brezillon@free-electrons.com, richard@nod.at,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Harry Chou <HarryYC.Chou@gmail.com>
Subject: [PATCH v2] mtd: spi-nor: Add support for Spansion S25FL064L
Date: Fri, 23 Jun 2017 03:58:11 +0800 [thread overview]
Message-ID: <1498161491-22411-1-git-send-email-HarryYC.Chou@gmail.com> (raw)
It's an 8 MiB flash with 4 KiB erase sectors.
Signed-off-by: Harry Chou <HarryYC.Chou@gmail.com>
---
Changes v1 -> v2:
- added SPI_NOR_DUAL_READ flag (supports Dual Output and I/O)
- added SPI_NOR_QUAD_READ flag (supports Quad Output and I/O)
- added SPI_NOR_4B_OPCODES flag (supports the 4-byte address instruction set)
drivers/mtd/spi-nor/spi-nor.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
index dea8c9c..9db5861 100644
--- a/drivers/mtd/spi-nor/spi-nor.c
+++ b/drivers/mtd/spi-nor/spi-nor.c
@@ -1076,6 +1076,7 @@ static const struct flash_info spi_nor_ids[] = {
{ "s25fl164k", INFO(0x014017, 0, 64 * 1024, 128, SECT_4K) },
{ "s25fl204k", INFO(0x014013, 0, 64 * 1024, 8, SECT_4K | SPI_NOR_DUAL_READ) },
{ "s25fl208k", INFO(0x014014, 0, 64 * 1024, 16, SECT_4K | SPI_NOR_DUAL_READ) },
+ { "s25fl064l", INFO(0x016017, 0, 64 * 1024, 128, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
/* SST -- large erase sizes are "overlays", "sectors" are 4K */
{ "sst25vf040b", INFO(0xbf258d, 0, 64 * 1024, 8, SECT_4K | SST_WRITE) },
--
2.7.4
next reply other threads:[~2017-06-22 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 19:58 Harry Chou [this message]
2017-06-26 21:09 ` [PATCH v2] mtd: spi-nor: Add support for Spansion S25FL064L Cyrille Pitchen
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=1498161491-22411-1-git-send-email-HarryYC.Chou@gmail.com \
--to=harryyc.chou@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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;
as well as URLs for NNTP newsgroup(s).