From: Haikun Wang <haikun.wang@freescale.com>
To: <linux-mtd@lists.infradead.org>
Cc: computersforpeace@gmail.com, dwmw2@infradead.org,
han.xu@freescale.com, Haikun Wang <haikun.wang@freescale.com>
Subject: [PATCH 1/2 v1] mtd: spi-nor: fsl-quadspi: Enable LS1021 support
Date: Fri, 24 Apr 2015 18:26:54 +0800 [thread overview]
Message-ID: <1429871214-44560-1-git-send-email-haikun.wang@freescale.com> (raw)
Add LS1021 QSPI chip special information
Signed-off-by: Haikun Wang <haikun.wang@freescale.com>
---
drivers/mtd/spi-nor/fsl-quadspi.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/mtd/spi-nor/fsl-quadspi.c b/drivers/mtd/spi-nor/fsl-quadspi.c
index 5d5d362..1742de9 100644
--- a/drivers/mtd/spi-nor/fsl-quadspi.c
+++ b/drivers/mtd/spi-nor/fsl-quadspi.c
@@ -194,6 +194,7 @@
enum fsl_qspi_devtype {
FSL_QUADSPI_VYBRID,
FSL_QUADSPI_IMX6SX,
+ FSL_QUADSPI_LS1,
};
struct fsl_qspi_devtype_data {
@@ -217,6 +218,12 @@ static struct fsl_qspi_devtype_data imx6sx_data = {
.ahb_buf_size = 1024
};
+static struct fsl_qspi_devtype_data ls1_data = {
+ .devtype = FSL_QUADSPI_LS1,
+ .rxfifo = 128,
+ .txfifo = 64;
+};
+
#define FSL_QSPI_MAX_CHIP 4
struct fsl_qspi {
struct mtd_info mtd[FSL_QSPI_MAX_CHIP];
@@ -665,6 +672,7 @@ static int fsl_qspi_nor_setup_last(struct fsl_qspi *q)
static struct of_device_id fsl_qspi_dt_ids[] = {
{ .compatible = "fsl,vf610-qspi", .data = (void *)&vybrid_data, },
{ .compatible = "fsl,imx6sx-qspi", .data = (void *)&imx6sx_data, },
+ { .compatible = "fsl,ls1-qspi", .data = (void *)&ls1_data, },
{ /* sentinel */ }
};
MODULE_DEVICE_TABLE(of, fsl_qspi_dt_ids);
--
2.1.0.27.g96db324
next reply other threads:[~2015-04-24 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 10:26 Haikun Wang [this message]
2015-05-20 17:23 ` [PATCH 1/2 v1] mtd: spi-nor: fsl-quadspi: Enable LS1021 support Brian Norris
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=1429871214-44560-1-git-send-email-haikun.wang@freescale.com \
--to=haikun.wang@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=han.xu@freescale.com \
--cc=linux-mtd@lists.infradead.org \
/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