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>,
"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 1/4] spi: add support for octal I/O data transfer
Date: Thu, 4 Oct 2018 11:19:41 +0200 [thread overview]
Message-ID: <20181004111941.0da33ec0@bbrezillon> (raw)
In-Reply-To: <VI1PR04MB10380FD9CE99E34BA27E55B699EA0@VI1PR04MB1038.eurprd04.prod.outlook.com>
On Thu, 4 Oct 2018 09:14:36 +0000
Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp.com> wrote:
> Hi Boris,
>
> > -----Original Message-----
> > From: Boris Brezillon [mailto:boris.brezillon@bootlin.com]
> > Sent: Thursday, October 4, 2018 2:35 PM
> > To: Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp.com>
> > Cc: linux-mtd@lists.infradead.org; marek.vasut@gmail.com;
> > vigneshr@ti.com; linux-spi@vger.kernel.org;
> > devicetree@vger.kernel.org; robh@kernel.org; mark.rutland@arm.com;
> > shawnguo@kernel.org; linux-arm- kernel@lists.infradead.org;
> > computersforpeace@gmail.com; frieder.schrempf@exceet.de;
> > linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/4] spi: add
> > support for octal I/O data transfer
> >
> > Hi Yogesh,
> >
> > On Thu, 4 Oct 2018 14:18:37 +0530
> > Yogesh Gaur <yogeshnarayan.gaur@nxp.com> wrote:
> >
> > > Add flags for Octal 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_OCTAL: transmit with 8 wires
> > > SPI_RX_OCTAL: receive with 8 wires
> > >
> > > Signed-off-by: Yogesh Gaur <yogeshnarayan.gaur@nxp.com>
> > > ---
> > > drivers/spi/spi.c | 6 ++++++
> > > include/linux/spi/spi.h | 2 ++
> > > 2 files changed, 8 insertions(+)
> > >
> > > diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c index
> > > ec395a6..80f672f 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_OCTAL;
> > > + 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_OCTAL;
> > > + break;
> > > default:
> > > dev_warn(&ctlr->dev,
> > > "spi-rx-bus-width %d not
> > > supported\n", diff --
> > git
> > > a/include/linux/spi/spi.h b/include/linux/spi/spi.h index
> > > a64235e..2d21307 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_OCTAL
> > > 0x1000 /* transmit with 8
> > wires */
> > > +#define SPI_RX_OCTAL
> > > 0x2000 /* receive with 8 wires
> > */
> > > int irq;
> > > void *controller_state;
> > > void *controller_data;
> >
> > You're still not updating spi-mem.c to check those flags and
> > SPI_MEM_MAX_BUSWIDTH is not updated to match the new limit (8
> > instead of 4).
> >
> Yes and its strange that my octal mode communication is working fine
> without adding support in spi-mem.c and that's why this has been
> missed from me.
Are you based on top of spi-next?
next prev parent reply other threads:[~2018-10-04 9:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 8:48 [PATCH 0/4] spi: add support for octal mode data transfer Yogesh Gaur
2018-10-04 8:48 ` [PATCH 1/4] spi: add support for octal I/O " Yogesh Gaur
2018-10-04 9:04 ` Boris Brezillon
2018-10-04 9:14 ` Yogesh Narayan Gaur
2018-10-04 9:19 ` Boris Brezillon [this message]
2018-10-04 9:25 ` Yogesh Narayan Gaur
2018-10-04 12:07 ` Yogesh Narayan Gaur
2018-10-04 12:12 ` Boris Brezillon
2018-10-04 8:48 ` [PATCH 2/4] mtd: spi-nor: add support for octal mode " Yogesh Gaur
2018-10-04 9:14 ` Boris Brezillon
2018-10-04 8:48 ` [PATCH 3/4] spi: nxp-fspi: add mode flag bit for octal support Yogesh Gaur
2018-10-04 8:48 ` [PATCH 4/4] arm64: dts: lx2160a: update fspi node Yogesh Gaur
2018-10-04 9:18 ` Boris Brezillon
2018-10-04 9:24 ` Yogesh Narayan Gaur
2018-10-04 9:26 ` Boris Brezillon
2018-10-04 9:27 ` Yogesh Narayan Gaur
2018-10-04 9:22 ` [PATCH 0/4] spi: add support for octal mode data transfer Vignesh R
2018-10-04 9:28 ` 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=20181004111941.0da33ec0@bbrezillon \
--to=boris.brezillon@bootlin.com \
--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).