From: Amelie DELAUNAY <amelie.delaunay@st.com>
To: "cezary.gapinski@gmail.com" <cezary.gapinski@gmail.com>,
Mark Brown <broonie@kernel.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH 0/5] Add support for STM32F4 SPI
Date: Mon, 10 Dec 2018 12:37:56 +0000 [thread overview]
Message-ID: <ede8544f-c71d-0901-5522-e97215d23f85@st.com> (raw)
In-Reply-To: <1544363636-12161-1-git-send-email-cezary.gapinski@gmail.com>
Hi Cezary,
On 12/9/18 2:53 PM, cezary.gapinski@gmail.com wrote:
> From: Cezary Gapinski <cezary.gapinski@gmail.com>
>
> This series of patches adds support for first generation of SPI interface
> for STM32F4 family.
>
First of all, thanks for adding STM32F4 SPI support.
> This version of driver is mostly different to STM32H7 one. Based on linux
> kernel I2C drivers for STM32 where drivers were splited into STM32F4 and
> STM32F7 family the same approach seems to be sufficient for SPI STM32
> drivers. Therefore STM32H7 driver was moved to spi-stm32h7.c file and
> register and functions were renamed to be more specific to STM32H7.
>
You're right, STM32F4 SPI is slightly different from STM32H7 one:
register map/bits offsets are different and STM32H7 has an RX and TX FIFO.
But if you have a look on STM32F7 SPI [1], you'll see that STM32F7 SPI
is based on STM32F4 SPI with new features (data frames & FIFOs) also
available on STM32H7 SPI.
That's why STM32H7 SPI driver was called spi-stm32. The goal was to use
compatible & match data to differentiate each STM32Fx specificities.
You can have a look on how it is managed in drivers/rtc/rtc-stm32.c (the
same driver covers 2 HW version of STM32 RTC), or in
drivers/iio/dac/stm32-dac-core.c and stm32-dac.c (the same driver also
covers 2 HW version of STM32 DAC).
As your spi-stm32f4.c file is highly based on the existing spi-stm32.c
file, I think that common code could be factored and specificities could
be handled with compatible and match data.
Regards,
Amelie
[1]
https://www.st.com/content/ccc/resource/technical/document/reference_manual/c5/cf/ef/52/c0/f1/4b/fa/DM00124865.pdf/files/DM00124865.pdf/jcr:content/translations/en.DM00124865.pdf
> For current version master mode with full-duplex and 8/16 bit data frame
> format are supported. There is no TX and RX FIFOs like in STM32H7.
> DMA capabilility is supported for messages longer than arbitrary number
> of bytes (that is set already to 16 bytes) when TX and RX channels are
> set at the same time.
>
> Cezary Gapinski (5):
> spi: stm32: rename STM32 SPI registers and functions to STM32H7
> spi: stm32: rename spi-stm32 to spi-stm32h7
> spi: stm32: add driver for STM32F4 controller
> ARM: dts: stm32: add SPI support on STM32F429 SoC
> spi: stm32: add description about STM32F4 bindings
>
> .../devicetree/bindings/spi/spi-stm32.txt | 9 +-
> arch/arm/boot/dts/stm32f429.dtsi | 60 +
> drivers/spi/Kconfig | 18 +-
> drivers/spi/Makefile | 3 +-
> drivers/spi/spi-stm32.c | 1322 -------------------
> drivers/spi/spi-stm32f4.c | 1002 +++++++++++++++
> drivers/spi/spi-stm32h7.c | 1340 ++++++++++++++++++++
> 7 files changed, 2424 insertions(+), 1330 deletions(-)
> delete mode 100644 drivers/spi/spi-stm32.c
> create mode 100644 drivers/spi/spi-stm32f4.c
> create mode 100644 drivers/spi/spi-stm32h7.c
>
next prev parent reply other threads:[~2018-12-10 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 13:53 cezary.gapinski
2018-12-09 13:53 ` [PATCH 1/5] spi: stm32: rename STM32 SPI registers and functions to STM32H7 cezary.gapinski
2018-12-09 13:53 ` [PATCH 2/5] spi: stm32: rename spi-stm32 to spi-stm32h7 cezary.gapinski
2018-12-09 13:53 ` [PATCH 3/5] spi: stm32: add driver for STM32F4 controller cezary.gapinski
2018-12-09 13:53 ` [PATCH 4/5] ARM: dts: stm32: add SPI support on STM32F429 SoC cezary.gapinski
2019-02-04 8:23 ` Alexandre Torgue
2018-12-09 13:53 ` [PATCH 5/5] spi: stm32: add description about STM32F4 bindings cezary.gapinski
2018-12-14 22:48 ` kbuild test robot
2018-12-20 19:49 ` Rob Herring
2018-12-10 12:37 ` Amelie DELAUNAY [this message]
2018-12-10 19:05 ` [PATCH 0/5] Add support for STM32F4 SPI Cezary Gapiński
2018-12-17 12:51 ` Amelie DELAUNAY
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=ede8544f-c71d-0901-5522-e97215d23f85@st.com \
--to=amelie.delaunay@st.com \
--cc=alexandre.torgue@st.com \
--cc=broonie@kernel.org \
--cc=cezary.gapinski@gmail.com \
--cc=devicetree@vger.kernel.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=mark.rutland@arm.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
all inboxes | Powered by JetHome®