From: Rob Herring <robh@kernel.org>
To: Alexandre TORGUE <alexandre.torgue@st.com>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@armlinux.org.uk>,
Olof Johansson <olof@lixom.net>,
lee.jones@linaro.org, Jonathan Corbet <corbet@lwn.net>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/8] Documentation: dt-bindings: Add STM32 pinctrl driver DT bindings
Date: Wed, 1 Feb 2017 11:31:50 -0600 [thread overview]
Message-ID: <20170201173150.lri7qgq52oflm2m7@rob-hp-laptop> (raw)
In-Reply-To: <1485868465-30446-4-git-send-email-alexandre.torgue@st.com>
On Tue, Jan 31, 2017 at 02:14:20PM +0100, Alexandre TORGUE wrote:
> Add compatible sting for stm32h743 MCU.
>
> Signed-off-by: Alexandre TORGUE <alexandre.torgue@st.com>
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.txt
> index b24583a..ac8dcb7 100644
> --- a/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.txt
> +++ b/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.txt
> @@ -10,6 +10,7 @@ Required properies:
> - compatible: value should be one of the following:
> (a) "st,stm32f429-pinctrl"
> (b) "st,stm32f746-pinctrl"
> + (c) "st,stm32h743-pinctrl"
Drop the a,b,c.
> - #address-cells: The value of this property must be 1
> - #size-cells : The value of this property must be 1
> - ranges : defines mapping between pin controller node (parent) to
> --
> 1.9.1
>
next prev parent reply other threads:[~2017-02-01 17:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 13:14 [PATCH 0/8] ADD STM32H743 MCU and STM32H743i-Eval board supports Alexandre TORGUE
2017-01-31 13:14 ` [PATCH 1/8] include: dt-bindings: Add STM32H7 pinctrl DT bindings Alexandre TORGUE
2017-02-06 8:37 ` Linus Walleij
2017-01-31 13:14 ` [PATCH 2/8] pinctrl: stm32: Add STM32H743 MCU support Alexandre TORGUE
2017-02-06 8:40 ` Linus Walleij
2017-01-31 13:14 ` [PATCH 3/8] Documentation: dt-bindings: Add STM32 pinctrl driver DT bindings Alexandre TORGUE
2017-02-01 17:31 ` Rob Herring [this message]
2017-02-01 17:33 ` Rob Herring
2017-02-06 8:43 ` Linus Walleij
2017-01-31 13:14 ` [PATCH 4/8] ARM: stm32: create dedicated kconfig for STM32 machine Alexandre TORGUE
2017-01-31 13:14 ` [PATCH 5/8] ARM: stm32: Add a new SOC - STM32H743 Alexandre TORGUE
2017-01-31 13:14 ` [PATCH 6/8] ARM: stm32: Introduce MACH_STM32H743 flag Alexandre TORGUE
2017-01-31 13:14 ` [PATCH 7/8] ARM: dts: stm32: Add STM32H743 MCU and STM32H743i-EVAL board Alexandre TORGUE
2017-01-31 13:14 ` [PATCH 8/8] ARM: configs: Add new config fragment to change RAM start point Alexandre TORGUE
2017-02-01 15:16 ` [PATCH 0/8] ADD STM32H743 MCU and STM32H743i-Eval board supports Linus Walleij
2017-02-01 16:47 ` Alexandre Torgue
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=20170201173150.lri7qgq52oflm2m7@rob-hp-laptop \
--to=robh@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--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 \
/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).