From: Alexandre Torgue <alexandre.torgue@st.com>
To: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@armlinux.org.uk>,
Olof Johansson <olof@lixom.net>,
Patrice Chotard <patrice.chotard@st.com>, <lee.jones@linaro.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 0/8] Add STM32F469 pinctrl and fix issues in STM32 pinctrl
Date: Mon, 30 Jan 2017 15:55:02 +0100 [thread overview]
Message-ID: <0df054a3-a0bf-7691-4546-4710bc8f32ce@st.com> (raw)
In-Reply-To: <1485533721-9019-1-git-send-email-alexandre.torgue@st.com>
Hi,
On 01/27/2017 05:15 PM, Alexandre TORGUE wrote:
> This series adds support of a dedicated driver for STM32F469 MCU pinctroller.
> This add generates some changes inside STM32 pinctrl driver and inside STM32
> device tree.
>
> Changes in STM32 pinctrl driver:
> -------------------------------
>
> - Add STM32F469 driver.
>
> - Change STM32 pinctrl core in order to use "gpio-ranges" devicetree definitions.
> Indeed, on STM32F469 there an hole in BANK J. We need to declare a gpio-ranges
> in gpioj controller node to handle this hole.
>
> Changes in STM32 device tree:
> ----------------------------
> I propose a new architecture (a new file split) for pinmux definition:
>
> - Create a common stm32f4-pinctrl.dtsi for pinmuxing definitions
> which are common between STM32F429 and STM32F469 MCU.
>
> - Create dedicated stm32fxxx-pinctrl.dtsi file for each MCU
> (stm32f429-pinctrl.dtsi and stm32f469-pinctrl.dtsi) each one will
> include stm32f4-pinctrl.dtsi. All differences (pinmuxing or GPIO
> bank holes) will be put inside the dedicated files.
>
> This series fix a locking issue when a gpio is used as IRQ.
>
> Regards
> Alex
>
> Alexandre TORGUE (8):
> pinctrl: stm32: fix bad location of gpiochip_lock_as_irq
> pinctrl: stm32: use gpio-ranges to declare bank range
I just see typo issue in patch 1&2. I will send a V2 when more review
will be done.
Regards
Alex
> Documentation: dt: Add bindings for STM32 pinctrl
> includes: dt-bindings: Rename STM32F429 pinctrl DT bindings
> pinctrl: stm32: Add STM32F469 MCU support
> Documentation: dt: Add new compatible to STM32 pinctrl driver bindings
> ARM: Kconfig: Introduce MACH_STM32F469 flag
> ARM: dts: stm32: create dedicated files for pinctrl definitions
>
> .../bindings/pinctrl/st,stm32-pinctrl.txt | 57 +-
> arch/arm/Kconfig | 5 +
> arch/arm/boot/dts/stm32429i-eval.dts | 1 +
> arch/arm/boot/dts/stm32f4-pinctrl.dtsi | 196 +++
> arch/arm/boot/dts/stm32f429-disco.dts | 1 +
> arch/arm/boot/dts/stm32f429-pinctrl.dtsi | 106 ++
> arch/arm/boot/dts/stm32f429.dtsi | 153 --
> arch/arm/boot/dts/stm32f469-disco.dts | 1 +
> arch/arm/boot/dts/stm32f469-pinctrl.dtsi | 107 ++
> drivers/pinctrl/stm32/Kconfig | 6 +
> drivers/pinctrl/stm32/Makefile | 1 +
> drivers/pinctrl/stm32/pinctrl-stm32.c | 129 +-
> drivers/pinctrl/stm32/pinctrl-stm32f469.c | 1574 ++++++++++++++++++++
> include/dt-bindings/pinctrl/stm32f4-pinfunc.h | 1302 ++++++++++++++++
> include/dt-bindings/pinctrl/stm32f429-pinfunc.h | 1239 ---------------
> 15 files changed, 3414 insertions(+), 1464 deletions(-)
> create mode 100644 arch/arm/boot/dts/stm32f4-pinctrl.dtsi
> create mode 100644 arch/arm/boot/dts/stm32f429-pinctrl.dtsi
> create mode 100644 arch/arm/boot/dts/stm32f469-pinctrl.dtsi
> create mode 100644 drivers/pinctrl/stm32/pinctrl-stm32f469.c
> create mode 100644 include/dt-bindings/pinctrl/stm32f4-pinfunc.h
> delete mode 100644 include/dt-bindings/pinctrl/stm32f429-pinfunc.h
>
prev parent reply other threads:[~2017-01-30 15:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 16:15 Alexandre TORGUE
2017-01-27 16:15 ` [PATCH 1/8] pinctrl: stm32: fix bad location of gpiochip_lock_as_irq Alexandre TORGUE
2017-01-30 15:15 ` Linus Walleij
2017-01-27 16:15 ` [PATCH 2/8] pinctrl: stm32: use gpio-ranges to declare bank range Alexandre TORGUE
2017-01-30 15:19 ` Linus Walleij
2017-01-30 16:29 ` Alexandre Torgue
2017-02-01 15:01 ` Linus Walleij
2017-03-27 10:23 ` Alexandre Torgue
2017-01-27 16:15 ` [PATCH 3/8] Documentation: dt: Add bindings for STM32 pinctrl Alexandre TORGUE
2017-02-01 15:04 ` Rob Herring
2017-02-06 8:45 ` Linus Walleij
2017-01-27 16:15 ` [PATCH 4/8] includes: dt-bindings: Rename STM32F429 pinctrl DT bindings Alexandre TORGUE
2017-01-27 16:15 ` [PATCH 5/8] pinctrl: stm32: Add STM32F469 MCU support Alexandre TORGUE
2017-01-27 16:15 ` [PATCH 6/8] Documentation: dt: Add new compatible to STM32 pinctrl driver bindings Alexandre TORGUE
2017-02-01 15:06 ` Rob Herring
2017-02-01 15:58 ` Alexandre Torgue
2017-02-06 8:46 ` Linus Walleij
2017-02-06 11:21 ` Alexandre Torgue
2017-01-27 16:15 ` [PATCH 7/8] ARM: Kconfig: Introduce MACH_STM32F469 flag Alexandre TORGUE
2017-01-27 16:15 ` [PATCH 8/8] ARM: dts: stm32: create dedicated files for pinctrl definitions Alexandre TORGUE
2017-01-30 14:55 ` 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=0df054a3-a0bf-7691-4546-4710bc8f32ce@st.com \
--to=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=olof@lixom.net \
--cc=patrice.chotard@st.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®