From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"frieder.schrempf@exceet.de" <frieder.schrempf@exceet.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/7] spi: add support for octo mode I/O data transfer
Date: Tue, 23 Oct 2018 11:48:44 +0200 [thread overview]
Message-ID: <20181023114844.7adfa054@bbrezillon> (raw)
In-Reply-To: <1540287311-1572-2-git-send-email-yogeshnarayan.gaur@nxp.com>
On Tue, 23 Oct 2018 09:37:06 +0000
Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp.com> wrote:
> Add flags for Octo mode I/O data transfer
> Required for the SPI controller which can do the data transfer (TX/RX)
> on 8 data lines e.g. NXP FlexSPI controller.
> SPI_TX_OCTO: transmit with 8 wires
> SPI_RX_OCTO: receive with 8 wires
>
> Signed-off-by: Yogesh Gaur <yogeshnarayan.gaur@nxp.com>
Reviewed-by: Boris Brezillon <boris.brezillon@bootlin.com>
> ---
> Changes for v3:
> - Modified string 'octal' with 'octo'.
> - Add octo mode support in spi_setup().
> Changes for v2:
> - Incorporated review comments of Boris.
>
> drivers/spi/spi.c | 12 ++++++++++--
> include/linux/spi/spi.h | 2 ++
> 2 files changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
> index ec395a6..6d57fa7 100644
> --- a/drivers/spi/spi.c
> +++ b/drivers/spi/spi.c
> @@ -1573,6 +1573,9 @@ static int of_spi_parse_dt(struct spi_controller *ctlr, struct spi_device *spi,
> case 4:
> spi->mode |= SPI_TX_QUAD;
> break;
> + case 8:
> + spi->mode |= SPI_TX_OCTO;
> + break;
> default:
> dev_warn(&ctlr->dev,
> "spi-tx-bus-width %d not supported\n",
> @@ -1591,6 +1594,9 @@ static int of_spi_parse_dt(struct spi_controller *ctlr, struct spi_device *spi,
> case 4:
> spi->mode |= SPI_RX_QUAD;
> break;
> + case 8:
> + spi->mode |= SPI_RX_OCTO;
> + break;
> default:
> dev_warn(&ctlr->dev,
> "spi-rx-bus-width %d not supported\n",
> @@ -2770,14 +2776,16 @@ int spi_setup(struct spi_device *spi)
> /* if it is SPI_3WIRE mode, DUAL and QUAD should be forbidden
> */
> if ((spi->mode & SPI_3WIRE) && (spi->mode &
> - (SPI_TX_DUAL | SPI_TX_QUAD | SPI_RX_DUAL | SPI_RX_QUAD)))
> + (SPI_TX_DUAL | SPI_TX_QUAD | SPI_TX_OCTO |
> + SPI_RX_DUAL | SPI_RX_QUAD | SPI_RX_OCTO)))
> return -EINVAL;
> /* help drivers fail *cleanly* when they need options
> * that aren't supported with their current controller
> */
> bad_bits = spi->mode & ~spi->controller->mode_bits;
> ugly_bits = bad_bits &
> - (SPI_TX_DUAL | SPI_TX_QUAD | SPI_RX_DUAL | SPI_RX_QUAD);
> + (SPI_TX_DUAL | SPI_TX_QUAD | SPI_TX_OCTO |
> + SPI_RX_DUAL | SPI_RX_QUAD | SPI_RX_OCTO);
> if (ugly_bits) {
> dev_warn(&spi->dev,
> "setup: ignoring unsupported mode bits %x\n",
> diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h
> index a64235e..cea4e49 100644
> --- a/include/linux/spi/spi.h
> +++ b/include/linux/spi/spi.h
> @@ -163,6 +163,8 @@ struct spi_device {
> #define SPI_TX_QUAD 0x200 /* transmit with 4 wires */
> #define SPI_RX_DUAL 0x400 /* receive with 2 wires */
> #define SPI_RX_QUAD 0x800 /* receive with 4 wires */
> +#define SPI_TX_OCTO 0x1000 /* transmit with 8 wires */
> +#define SPI_RX_OCTO 0x2000 /* receive with 8 wires */
> int irq;
> void *controller_state;
> void *controller_data;
next prev parent reply other threads:[~2018-10-23 9:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 9:37 [PATCH v3 0/7] spi: add support for octo mode Yogesh Narayan Gaur
2018-10-23 9:37 ` [PATCH v3 1/7] spi: add support for octo mode I/O data transfer Yogesh Narayan Gaur
2018-10-23 9:48 ` Boris Brezillon [this message]
2018-10-23 9:37 ` [PATCH v3 2/7] spi: spi-mem: " Yogesh Narayan Gaur
2018-10-23 9:49 ` Boris Brezillon
2018-10-23 9:37 ` [PATCH v3 3/7] mtd: spi-nor: add opcodes for octo Read/Write commands Yogesh Narayan Gaur
2018-10-23 9:37 ` [PATCH v3 4/7] mtd: spi-nor: add octo read flag for flash mt35xu512aba Yogesh Narayan Gaur
2018-10-23 9:37 ` [PATCH v3 5/7] mtd: m25p80: add support of octo mode I/O transfer Yogesh Narayan Gaur
2018-10-23 9:37 ` [PATCH v3 6/7] spi: nxp-fspi: add octo mode flag bit for octal support Yogesh Narayan Gaur
2018-10-23 9:37 ` [PATCH v3 7/7] arm64: dts: lx2160a: update fspi node Yogesh Narayan Gaur
2018-11-13 8:00 ` [PATCH v3 0/7] spi: add support for octo mode Vignesh R
2018-11-22 5:19 ` Yogesh Narayan Gaur
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=20181023114844.7adfa054@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frieder.schrempf@exceet.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--cc=vigneshr@ti.com \
--cc=yogeshnarayan.gaur@nxp.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).