From: Ludovic Barre <ludovic.Barre@st.com>
To: Mark Brown <broonie@kernel.org>,
Marek Vasut <marek.vasut@gmail.com>,
Boris Brezillon <boris.brezillon@bootlin.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
<linux-spi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<devicetree@vger.kernel.org>,
Ludovic Barre <ludovic.barre@st.com>
Subject: [PATCH 0/2] spi: spi-mem: add stm32 qspi controller
Date: Fri, 5 Oct 2018 09:43:01 +0200 [thread overview]
Message-ID: <1538725383-19781-1-git-send-email-ludovic.Barre@st.com> (raw)
From: Ludovic Barre <ludovic.barre@st.com>
The goal of this serie is to add support of qspi controller for stm32.
It is a specialized communication interface targeting single,
dual or quad SPI Flash memories (NOR/NAND).
Ludovic Barre (2):
dt-bindings: spi: add stm32 qspi controller
spi: spi-mem: add stm32 qspi controller
.../devicetree/bindings/spi/spi-stm32-qspi.txt | 44 ++
drivers/spi/Kconfig | 9 +
drivers/spi/Makefile | 1 +
drivers/spi/spi-stm32-qspi.c | 512 +++++++++++++++++++++
4 files changed, 566 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/spi-stm32-qspi.txt
create mode 100644 drivers/spi/spi-stm32-qspi.c
--
2.7.4
next reply other threads:[~2018-10-05 7:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 7:43 Ludovic Barre [this message]
2018-10-05 7:43 ` [PATCH 1/2] dt-bindings: spi: add stm32 qspi controller Ludovic Barre
2018-10-16 22:36 ` Rob Herring
2018-10-19 12:29 ` Applied "dt-bindings: spi: add stm32 qspi controller" to the spi tree Mark Brown
2018-10-05 7:43 ` [PATCH 2/2] spi: spi-mem: add stm32 qspi controller Ludovic Barre
2018-10-05 7:55 ` [Linux-stm32] " Loic PALLARDY
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=1538725383-19781-1-git-send-email-ludovic.Barre@st.com \
--to=ludovic.barre@st.com \
--cc=alexandre.torgue@st.com \
--cc=boris.brezillon@bootlin.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marek.vasut@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).