From: Palmer Dabbelt <palmer@sifive.com>
To: marek.vasut@gmail.com
Cc: dwmw2@infradead.org, computersforpeace@gmail.com,
boris.brezillon@bootlin.com, richard@nod.at,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Paul Walmsley <paul.walmsley@sifive.com>,
"Wesley W. Terpstra" <wesley@sifive.com>,
Palmer Dabbelt <palmer@sifive.com>
Subject: [PATCH v2 2/2] spi-nor: add support for is25wp256
Date: Tue, 7 Aug 2018 12:40:59 -0700 [thread overview]
Message-ID: <20180807194059.26348-3-palmer@sifive.com> (raw)
In-Reply-To: <20180807194059.26348-1-palmer@sifive.com>
From: "Wesley W. Terpstra" <wesley@sifive.com>
This is used of the HiFive Unleashed development board, and follows the
pattern of similar ISSI devices already listed.
Signed-off-by: Wesley W. Terpstra <wesley@sifive.com>
Signed-off-by: Palmer Dabbelt <palmer@sifive.com>
---
drivers/mtd/spi-nor/spi-nor.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
index aab93463a5e7..f10017b4543d 100644
--- a/drivers/mtd/spi-nor/spi-nor.c
+++ b/drivers/mtd/spi-nor/spi-nor.c
@@ -1072,6 +1072,8 @@ static const struct flash_info spi_nor_ids[] = {
SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) },
{ "is25wp128", INFO(0x9d7018, 0, 64 * 1024, 256,
SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) },
+ { "is25wp256", INFO(0x9d7019, 0, 64 * 1024, 512,
+ SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) },
/* Macronix */
{ "mx25l512e", INFO(0xc22010, 0, 64 * 1024, 1, SECT_4K) },
--
2.16.4
next prev parent reply other threads:[~2018-08-07 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 19:40 [PATCH v2 0/2] spi-nor: add support for is25wp256 Palmer Dabbelt
2018-08-07 19:40 ` [PATCH v2 1/2] spi-nor: add support for ISSI's block unlocking scheme Palmer Dabbelt
2019-02-13 16:23 ` Tudor.Ambarus
2018-08-07 19:40 ` Palmer Dabbelt [this message]
2019-02-13 17:27 ` [PATCH v2 2/2] spi-nor: add support for is25wp256 Tudor.Ambarus
2019-02-13 17:37 ` Tudor.Ambarus
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=20180807194059.26348-3-palmer@sifive.com \
--to=palmer@sifive.com \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=paul.walmsley@sifive.com \
--cc=richard@nod.at \
--cc=wesley@sifive.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;
as well as URLs for NNTP newsgroup(s).