From: Patrice Chotard <[email protected]>
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 | 125 +++++++++++++++++++++--
3 files changed, 159 insertions(+), 28 deletions(-)
--
2.25.1
On Tue, 16 Aug 2022 18:13:42 +0200, [email protected] wrote:
> From: Patrice Chotard <[email protected]>
>
> 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.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[2/2] spi: stm32_qspi: Add transfer_one_message() spi callback
commit: b051161f44d414e736fa2b011245441bae9babd7
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark