From: Conor Dooley <conor@kernel.org>
To: Ben Wolsieffer <ben.wolsieffer@hefring.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, 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>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Alain Volmat <alain.volmat@foss.st.com>,
Erwan Leray <erwan.leray@foss.st.com>,
Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Subject: Re: [PATCH v2 3/5] dt-bindings: spi: add stm32f7-spi compatible
Date: Fri, 3 Nov 2023 12:50:53 +0000 [thread overview]
Message-ID: <20231103-recognize-unwashed-b8f1a83fe851@spud> (raw)
In-Reply-To: <20231102193722.3042245-4-ben.wolsieffer@hefring.com>
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
On Thu, Nov 02, 2023 at 03:37:20PM -0400, Ben Wolsieffer wrote:
> The STM32F7 SPI peripheral is nearly identical to the STM32F4, with the
> only significant differences being support for a wider range of word
> sizes and the addition of 32-bit transmit and receive FIFOs.
A wider range of supported word sizes and some additional buffers,
implies that the F4 could be used as a fallback compatible. Does the
register map change incompatibly in the process of widening the FIFOs or
something like that?
Cheers,
Conor.
>
> Signed-off-by: Ben Wolsieffer <ben.wolsieffer@hefring.com>
> ---
> Documentation/devicetree/bindings/spi/st,stm32-spi.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/spi/st,stm32-spi.yaml b/Documentation/devicetree/bindings/spi/st,stm32-spi.yaml
> index ae0f082bd377..5754d603f34f 100644
> --- a/Documentation/devicetree/bindings/spi/st,stm32-spi.yaml
> +++ b/Documentation/devicetree/bindings/spi/st,stm32-spi.yaml
> @@ -23,6 +23,7 @@ properties:
> compatible:
> enum:
> - st,stm32f4-spi
> + - st,stm32f7-spi
> - st,stm32h7-spi
>
> reg:
> --
> 2.42.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-11-03 12:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 19:37 [PATCH v2 0/5] Add STM32F7 SPI support Ben Wolsieffer
2023-11-02 19:37 ` [PATCH v2 1/5] spi: stm32: rename stm32f4_* to stm32fx_* Ben Wolsieffer
2023-11-02 19:37 ` [PATCH v2 2/5] spi: stm32: use callbacks for read_rx and write_tx Ben Wolsieffer
2023-11-02 19:37 ` [PATCH v2 3/5] dt-bindings: spi: add stm32f7-spi compatible Ben Wolsieffer
2023-11-03 12:50 ` Conor Dooley [this message]
2023-11-03 13:29 ` Ben Wolsieffer
2023-11-03 14:51 ` Conor Dooley
2023-11-02 19:37 ` [PATCH v2 4/5] spi: stm32: add STM32F7 support Ben Wolsieffer
2023-11-02 19:37 ` [PATCH v2 5/5] ARM: dts: stm32: add SPI support on STM32F746 Ben Wolsieffer
2023-11-21 14:52 ` Alexandre TORGUE
2023-11-13 19:40 ` (subset) [PATCH v2 0/5] Add STM32F7 SPI support 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=20231103-recognize-unwashed-b8f1a83fe851@spud \
--to=conor@kernel.org \
--cc=alain.volmat@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=ben.wolsieffer@hefring.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 NNTP newsgroup(s).