From: Artur Jedrysek <jartur@cadence.com>
To: <linux-mtd@lists.infradead.org>
Cc: <linux-kernel@vger.kernel.org>,
Cyrille Pitchen <cyrille.pitchen@atmel.com>,
Marek Vasut <marek.vasut@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Richard Weinberger <richard@nod.at>,
Artur Jedrysek <jartur@cadence.com>
Subject: [PATCH 2/3] mtd: spi-nor: Add Octal SPI support to Cadence QSPI driver.
Date: Mon, 6 Mar 2017 12:32:25 +0000 [thread overview]
Message-ID: <1488803545-22461-1-git-send-email-jartur@cadence.com> (raw)
Recent versions of Cadence QSPI controller support Octal SPI transfers
as well. This patch updates existing driver to support such feature.
It is not possible to determine whether or not octal mode is supported
just by looking at revision register alone. To solve that, an additional
property in Device Tree is added to indicate such capability.
Both (revision and DT property) are used to determine, which mode to
pass to spi_nor_scan() call.
Additionally, the driver works on Xtensa CPU, hence Kconfig update.
Signed-off-by: Artur Jedrysek <jartur@cadence.com>
---
drivers/mtd/spi-nor/Kconfig | 2 +-
drivers/mtd/spi-nor/cadence-quadspi.c | 40 ++++++++++++++++++++++++++++++++++-
2 files changed, 40 insertions(+), 2 deletions(-)
diff --git a/drivers/mtd/spi-nor/Kconfig b/drivers/mtd/spi-nor/Kconfig
index 7252087..f195749 100644
--- a/drivers/mtd/spi-nor/Kconfig
+++ b/drivers/mtd/spi-nor/Kconfig
@@ -50,7 +50,7 @@ config SPI_ATMEL_QUADSPI
config SPI_CADENCE_QUADSPI
tristate "Cadence Quad SPI controller"
- depends on OF && (ARM || COMPILE_TEST)
+ depends on OF && (ARM || XTENSA || COMPILE_TEST)
help
Enable support for the Cadence Quad SPI Flash controller.
diff --git a/drivers/mtd/spi-nor/cadence-quadspi.c b/drivers/mtd/spi-nor/cadence-quadspi.c
index 9f8102d..5c06102 100644
--- a/drivers/mtd/spi-nor/cadence-quadspi.c
+++ b/drivers/mtd/spi-nor/cadence-quadspi.c
@@ -87,6 +87,7 @@ struct cqspi_st {
#define CQSPI_INST_TYPE_SINGLE 0
#define CQSPI_INST_TYPE_DUAL 1
#define CQSPI_INST_TYPE_QUAD 2
+#define CQSPI_INST_TYPE_OCTAL 3
#define CQSPI_DUMMY_CLKS_PER_BYTE 8
#define CQSPI_DUMMY_BYTES_MAX 4
@@ -204,6 +205,14 @@ struct cqspi_st {
#define CQSPI_REG_CMDWRITEDATALOWER 0xA8
#define CQSPI_REG_CMDWRITEDATAUPPER 0xAC
+#define CQSPI_REG_MODULEID 0xFC
+#define CQSPI_REG_MODULEID_CONF_ID_MASK 0x3
+#define CQSPI_REG_MODULEID_CONF_ID_LSB 0
+#define CQSPI_REG_MODULEID_CONF_ID_OCTAL_PHY 0x0
+#define CQSPI_REG_MODULEID_CONF_ID_OCTAL 0x1
+#define CQSPI_REG_MODULEID_CONF_ID_QUAD_PHY 0x2
+#define CQSPI_REG_MODULEID_CONF_ID_QUAD 0x3
+
/* Interrupt status bits */
#define CQSPI_REG_IRQ_MODE_ERR BIT(0)
#define CQSPI_REG_IRQ_UNDERFLOW BIT(1)
@@ -866,6 +875,9 @@ static int cqspi_set_protocol(struct spi_nor *nor, const int read)
case SPI_NOR_QUAD:
f_pdata->data_width = CQSPI_INST_TYPE_QUAD;
break;
+ case SPI_NOR_OCTAL:
+ f_pdata->data_width = CQSPI_INST_TYPE_OCTAL;
+ break;
default:
return -EINVAL;
}
@@ -1074,9 +1086,35 @@ static int cqspi_setup_flash(struct cqspi_st *cqspi, struct device_node *np)
struct cqspi_flash_pdata *f_pdata;
struct spi_nor *nor;
struct mtd_info *mtd;
+ enum read_mode mode;
+ enum read_mode dt_mode = SPI_NOR_QUAD;
unsigned int cs;
+ unsigned int rev_reg;
int i, ret;
+ /* Determine, whether or not octal transfer MAY be supported */
+ rev_reg = readl(cqspi->iobase + CQSPI_REG_MODULEID);
+ dev_info(dev, "CQSPI Module id %x\n", rev_reg);
+
+ switch (rev_reg & CQSPI_REG_MODULEID_CONF_ID_MASK) {
+ case CQSPI_REG_MODULEID_CONF_ID_OCTAL_PHY:
+ case CQSPI_REG_MODULEID_CONF_ID_OCTAL:
+ mode = SPI_NOR_OCTAL;
+ break;
+ case CQSPI_REG_MODULEID_CONF_ID_QUAD:
+ case CQSPI_REG_MODULEID_CONF_ID_QUAD_PHY:
+ mode = SPI_NOR_QUAD;
+ break;
+ }
+
+ if (of_property_read_bool(np, "cdns,octal-controller"))
+ dt_mode = SPI_NOR_OCTAL;
+
+ if (mode == SPI_NOR_QUAD && dt_mode == SPI_NOR_OCTAL)
+ dev_warn(dev, "Requested octal mode is not supported by the device.");
+ else if (mode == SPI_NOR_OCTAL && dt_mode == SPI_NOR_QUAD)
+ mode = SPI_NOR_QUAD;
+
/* Get flash device data */
for_each_available_child_of_node(dev->of_node, np) {
ret = of_property_read_u32(np, "reg", &cs);
@@ -1123,7 +1161,7 @@ static int cqspi_setup_flash(struct cqspi_st *cqspi, struct device_node *np)
goto err;
}
- ret = spi_nor_scan(nor, NULL, SPI_NOR_QUAD);
+ ret = spi_nor_scan(nor, NULL, mode);
if (ret)
goto err;
--
2.2.2
next reply other threads:[~2017-03-06 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 12:32 Artur Jedrysek [this message]
2017-03-06 21:21 ` Boris Brezillon
2017-03-07 8:26 ` Artur Jedrysek
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=1488803545-22461-1-git-send-email-jartur@cadence.com \
--to=jartur@cadence.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--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
all inboxes | Powered by JetHome®