From: Tim Harvey <tharvey@gateworks.com>
To: devicetree@vger.kernel.org, NXP Linux Team <linux-imx@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, Tim Harvey <tharvey@gateworks.com>
Subject: [PATCH 2/4] mtd: spi-nor: fujitsu: add support for MB85RS4MT
Date: Tue, 9 Mar 2021 14:00:12 -0800 [thread overview]
Message-ID: <20210309220014.22205-2-tharvey@gateworks.com> (raw)
In-Reply-To: <20210309220014.22205-1-tharvey@gateworks.com>
Add support for the Fujitsu MB85RS4MT SPI FRAM EEPROM device.
This is a 512KiB FRAM EEPROM.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
---
drivers/mtd/spi-nor/fujitsu.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mtd/spi-nor/fujitsu.c b/drivers/mtd/spi-nor/fujitsu.c
index e385d93e756c..9df5d0576cea 100644
--- a/drivers/mtd/spi-nor/fujitsu.c
+++ b/drivers/mtd/spi-nor/fujitsu.c
@@ -11,6 +11,7 @@
static const struct flash_info fujitsu_parts[] = {
/* Fujitsu */
{ "mb85rs1mt", INFO(0x047f27, 0, 128 * 1024, 1, SPI_NOR_NO_ERASE) },
+ { "mb85rs4mt", INFO(0x047f49, 0, 512 * 1024, 1, SPI_NOR_NO_ERASE) },
};
const struct spi_nor_manufacturer spi_nor_fujitsu = {
--
2.17.1
next prev parent reply other threads:[~2021-03-09 22:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 22:00 [PATCH 1/4] dt-bindings: at25: add Fujitsu MB85RS4MT Tim Harvey
2021-03-09 22:00 ` Tim Harvey [this message]
2021-03-09 22:00 ` [PATCH 3/4] dt-bindings: arm: imx: add imx8mm gw7901 support Tim Harvey
2021-03-16 22:23 ` Rob Herring
2021-03-09 22:00 ` [PATCH 4/4] arm64: dts: imx: Add i.mx8mm Gateworks gw7901 dts support Tim Harvey
2021-03-09 22:59 ` [PATCH 1/4] dt-bindings: at25: add Fujitsu MB85RS4MT Michael Walle
2021-03-10 5:33 ` Tudor.Ambarus
2021-03-11 22:39 ` Tim Harvey
2021-03-11 1:52 ` Tim Harvey
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=20210309220014.22205-2-tharvey@gateworks.com \
--to=tharvey@gateworks.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tudor.ambarus@microchip.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).