From: <patrice.chotard@foss.st.com>
To: Mark Brown <broonie@kernel.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>
Cc: <linux-spi@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <christophe.kerello@foss.st.com>,
<patrice.chotard@foss.st.com>, <devicetree@vger.kernel.org>
Subject: [PATCH v2 0/2] spi: stm32_qspi: use QSPI bus as 8 lines communication channel
Date: Wed, 10 Aug 2022 11:32:13 +0200 [thread overview]
Message-ID: <20220810093215.794977-1-patrice.chotard@foss.st.com> (raw)
From: Patrice Chotard <patrice.chotard@foss.st.com>
The goal of this series is to allow to use QSPI bus as a 8 lines communication
channel for specific purpose.
The QSPI block offers the possibility to communicate with 2 flashes in
parrallel using the dual flash mode, 8 data lines are then used.
Usage of DT parallel-memories property is needed to enable dual flash mode.
The addition of the legacy transfer_one_message() spi callback is also needed
as currently the stm32-qspi driver only supports spi_controller_mem_ops API.
arch/arm/boot/dts/stm32mp15-pinctrl.dtsi | 50 +++++++----
arch/arm/boot/dts/stm32mp157c-ev1.dts | 12 ++-
drivers/spi/spi-stm32-qspi.c | 103 +++++++++++++++++++++--
3 files changed, 139 insertions(+), 26 deletions(-)
--
2.25.1
next reply other threads:[~2022-08-10 9:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 9:32 patrice.chotard [this message]
2022-08-10 9:32 ` [PATCH v2 1/2] spi: stm32_qspi: Add transfer_one_message() spi callback patrice.chotard
2022-08-10 13:06 ` Mark Brown
2022-08-10 13:15 ` Patrice CHOTARD
2022-08-10 13:23 ` Mark Brown
2022-08-10 13:31 ` Patrice CHOTARD
2022-08-10 13:40 ` Mark Brown
2022-08-10 13:52 ` Patrice CHOTARD
2022-08-10 13:57 ` Mark Brown
2022-08-10 9:32 ` [PATCH v2 2/2] ARM: dts: stm32: Create separate pinmux for qspi cs pin in stm32mp15-pinctrl.dtsi patrice.chotard
2022-08-22 16:05 ` (subset) [PATCH v2 0/2] spi: stm32_qspi: use QSPI bus as 8 lines communication channel Mark Brown
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=20220810093215.794977-1-patrice.chotard@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=broonie@kernel.org \
--cc=christophe.kerello@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.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=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).