From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Alain Volmat <alain.volmat@foss.st.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Erwan Leray <erwan.leray@foss.st.com>,
Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Cc: <linux-spi@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/6] spi: stm32: add support for stm32mp25
Date: Thu, 25 Apr 2024 10:21:17 +0200 [thread overview]
Message-ID: <c217117d-6388-4230-8afa-d26226bb11ce@foss.st.com> (raw)
In-Reply-To: <20231218155721.359198-1-alain.volmat@foss.st.com>
Hi Alain
On 12/18/23 16:57, Alain Volmat wrote:
> This series adds support for spi bus found on the stm32mp25 and add
> all instances within device-trees.
>
> Alain Volmat (4):
> spi: stm32: use dma_get_slave_caps prior to configuring dma channel
> arm64: dts: st: add all 8 spi nodes on stm32mp251
> arm64: dts: st: add spi3/spi8 pins for stm32mp25
> arm64: dts: st: add spi3 / spi8 properties on stm32mp257f-ev1
>
> Valentin Caron (2):
> dt-bindings: spi: stm32: add st,stm32mp25-spi compatible
> spi: stm32: add st,stm32mp25-spi compatible supporting STM32MP25 soc
>
> .../devicetree/bindings/spi/st,stm32-spi.yaml | 1 +
> arch/arm64/boot/dts/st/stm32mp25-pinctrl.dtsi | 46 ++++++
> arch/arm64/boot/dts/st/stm32mp251.dtsi | 88 +++++++++++
> arch/arm64/boot/dts/st/stm32mp257f-ev1.dts | 14 ++
> drivers/spi/spi-stm32.c | 145 ++++++++++++++++--
> 5 files changed, 280 insertions(+), 14 deletions(-)
>
DT patches applied on stm32-next.
I added "access-controller" bindings for all SPI nodes.
Cheers
Alex
prev parent reply other threads:[~2024-04-25 8:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 15:57 [PATCH 0/6] spi: stm32: add support for stm32mp25 Alain Volmat
2023-12-18 15:57 ` [PATCH 1/6] spi: stm32: use dma_get_slave_caps prior to configuring dma channel Alain Volmat
2023-12-18 15:57 ` [PATCH 2/6] dt-bindings: spi: stm32: add st,stm32mp25-spi compatible Alain Volmat
2023-12-18 16:58 ` Fabrice Gasnier
2023-12-19 16:39 ` Conor Dooley
2023-12-18 15:57 ` [PATCH 3/6] spi: stm32: add st,stm32mp25-spi compatible supporting STM32MP25 soc Alain Volmat
2023-12-18 15:57 ` [PATCH 4/6] arm64: dts: st: add all 8 spi nodes on stm32mp251 Alain Volmat
2023-12-18 15:57 ` [PATCH 5/6] arm64: dts: st: add spi3/spi8 pins for stm32mp25 Alain Volmat
2023-12-18 15:57 ` [PATCH 6/6] arm64: dts: st: add spi3 / spi8 properties on stm32mp257f-ev1 Alain Volmat
2023-12-22 13:30 ` (subset) [PATCH 0/6] spi: stm32: add support for stm32mp25 Mark Brown
2024-04-25 8:21 ` Alexandre TORGUE [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=c217117d-6388-4230-8afa-d26226bb11ce@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=alain.volmat@foss.st.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=erwan.leray@foss.st.com \
--cc=fabrice.gasnier@foss.st.com \
--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=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 read-only IMAP folder(s) and NNTP newsgroup(s).