From: Marek Vasut <marek.vasut@gmail.com>
To: Cyrille Pitchen <cyrille.pitchen@atmel.com>,
linux-mtd@lists.infradead.org
Cc: computersforpeace@gmail.com, dwmw2@infradead.org,
boris.brezillon@free-electrons.com, richard@nod.at,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 4/4] mtd: spi-nor: introduce Octo SPI protocols
Date: Wed, 19 Apr 2017 01:06:43 +0200 [thread overview]
Message-ID: <4563f2e7-0f3b-4b4e-58d8-40b4653429f0@gmail.com> (raw)
In-Reply-To: <fa0c5c607bcc0916c0f8f66e24d717f326054573.1492554665.git.cyrille.pitchen@atmel.com>
On 04/19/2017 12:51 AM, Cyrille Pitchen wrote:
> This patch starts adding support to Octo SPI protocols (SPI x-y-8).
>
> Op codes for Fast Read and/or Page Program operations using Octo SPI
> protocols are not known yet (no JEDEC specification has defined them yet)
> but we'd rather introduce the Octo SPI protocols now so it's done as it
> should be.
>
> Signed-off-by: Cyrille Pitchen <cyrille.pitchen@atmel.com>
Reviewed-by: Marek Vasut <marek.vasut@gmail.com>
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2017-04-18 23:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 22:51 [PATCH v7 0/4] mtd: spi-nor: parse SFDP tables to setup (Q)SPI memories Cyrille Pitchen
2017-04-18 22:51 ` [PATCH v7 1/4] mtd: spi-nor: introduce SPI 1-2-2 and SPI 1-4-4 protocols Cyrille Pitchen
2017-04-18 23:02 ` Marek Vasut
2017-04-19 20:12 ` Cyrille Pitchen
2017-04-19 20:49 ` Cyrille Pitchen
2017-04-19 21:31 ` Marek Vasut
2017-04-19 23:17 ` Cyrille Pitchen
2017-04-20 1:56 ` Marek Vasut
2017-04-18 22:51 ` [PATCH v7 2/4] mtd: m25p80: add support of SPI 1-2-2 and " Cyrille Pitchen
2017-04-18 22:51 ` [PATCH v7 3/4] mtd: spi-nor: introduce Double Transfer Rate (DTR) SPI protocols Cyrille Pitchen
2017-04-18 23:05 ` Marek Vasut
2017-04-19 20:20 ` Cyrille Pitchen
2017-04-19 21:35 ` Marek Vasut
2017-04-18 22:51 ` [PATCH v7 4/4] mtd: spi-nor: introduce Octo " Cyrille Pitchen
2017-04-18 23:06 ` Marek Vasut [this message]
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=4563f2e7-0f3b-4b4e-58d8-40b4653429f0@gmail.com \
--to=marek.vasut@gmail.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=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;
as well as URLs for NNTP newsgroup(s).