From: Mark Brown <broonie@kernel.org>
To: Valentin Caron <valentin.caron@foss.st.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Alain Volmat <alain.volmat@foss.st.com>,
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 v2 0/4] spi: stm32: add spi slave mode
Date: Wed, 14 Jun 2023 13:16:10 +0100 [thread overview]
Message-ID: <d0b62ef2-5355-4c00-9ff6-4ea9995ec0e1@sirena.org.uk> (raw)
In-Reply-To: <20230614102628.202936-1-valentin.caron@foss.st.com>
[-- Attachment #1: Type: text/plain, Size: 212 bytes --]
On Wed, Jun 14, 2023 at 12:26:23PM +0200, Valentin Caron wrote:
> STM32 SPI can operate in slave mode.
> This series add this functionnality in spi-stm32 driver.
The more modern terminology here is device mode.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-06-14 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 10:26 [PATCH v2 0/4] spi: stm32: add spi slave mode Valentin Caron
2023-06-14 10:26 ` [PATCH v2 1/4] spi: stm32: renaming of spi_master into spi_controller Valentin Caron
2023-06-14 10:26 ` [PATCH v2 2/4] spi: stm32: use dmaengine_terminate_{a}sync instead of _all Valentin Caron
2023-06-14 10:26 ` [PATCH v2 3/4] dt-bindings: spi: stm32: disable spi-slave property for stm32f4-f7 Valentin Caron
2023-06-14 10:26 ` [PATCH v2 4/4] spi: stm32: introduction of stm32h7 SPI slave support Valentin Caron
2023-06-14 12:16 ` Mark Brown [this message]
2023-06-15 8:05 ` [PATCH v2 0/4] spi: stm32: add spi slave mode Valentin CARON
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=d0b62ef2-5355-4c00-9ff6-4ea9995ec0e1@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alain.volmat@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--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 \
--cc=valentin.caron@foss.st.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: 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).