From: <patrice.chotard@foss.st.com> To: Mark Brown <broonie@kernel.org>, Alexandre Torgue <alexandre.torgue@foss.st.com> 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> Subject: [PATCH v4 0/2] spi: stm32_qspi: use QSPI bus as 8 lines communication channel Date: Tue, 23 Aug 2022 09:58:48 +0200 [thread overview] Message-ID: <20220823075850.575043-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 cs-gpios populated and spi-tx-bus-width / spi-rx-bus-width both set to 8, 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. Patrice Chotard (2): ARM: dts: stm32: Create separate pinmux for qspi cs pin in stm32mp15-pinctrl.dtsi spi: stm32_qspi: Add transfer_one_message() spi callback arch/arm/boot/dts/stm32mp15-pinctrl.dtsi | 50 ++++++---- arch/arm/boot/dts/stm32mp157c-ev1.dts | 12 ++- drivers/spi/spi-stm32-qspi.c | 118 +++++++++++++++++++++-- 3 files changed, 152 insertions(+), 28 deletions(-) -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: <patrice.chotard@foss.st.com> To: Mark Brown <broonie@kernel.org>, Alexandre Torgue <alexandre.torgue@foss.st.com> 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> Subject: [PATCH v4 0/2] spi: stm32_qspi: use QSPI bus as 8 lines communication channel Date: Tue, 23 Aug 2022 09:58:48 +0200 [thread overview] Message-ID: <20220823075850.575043-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 cs-gpios populated and spi-tx-bus-width / spi-rx-bus-width both set to 8, 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. Patrice Chotard (2): ARM: dts: stm32: Create separate pinmux for qspi cs pin in stm32mp15-pinctrl.dtsi spi: stm32_qspi: Add transfer_one_message() spi callback arch/arm/boot/dts/stm32mp15-pinctrl.dtsi | 50 ++++++---- arch/arm/boot/dts/stm32mp157c-ev1.dts | 12 ++- drivers/spi/spi-stm32-qspi.c | 118 +++++++++++++++++++++-- 3 files changed, 152 insertions(+), 28 deletions(-) -- 2.25.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-08-23 7:59 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-23 7:58 patrice.chotard [this message] 2022-08-23 7:58 ` [PATCH v4 0/2] spi: stm32_qspi: use QSPI bus as 8 lines communication channel patrice.chotard 2022-08-23 7:58 ` [PATCH v4 1/2] ARM: dts: stm32: Create separate pinmux for qspi cs pin in stm32mp15-pinctrl.dtsi patrice.chotard 2022-08-23 7:58 ` patrice.chotard 2022-08-26 8:44 ` Alexandre TORGUE 2022-08-26 8:44 ` Alexandre TORGUE 2022-08-23 7:58 ` [PATCH v4 2/2] spi: stm32_qspi: Add transfer_one_message() spi callback patrice.chotard 2022-08-23 7:58 ` patrice.chotard 2022-08-23 16:32 ` (subset) [PATCH v4 0/2] spi: stm32_qspi: use QSPI bus as 8 lines communication channel Mark Brown 2022-08-23 16:32 ` 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=20220823075850.575043-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=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 \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.