From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Jagan Teki <jagan@amarulasolutions.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Rob Herring <robh+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-amarula@amarulasolutions.com>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: stm32: Add STM32MP1 I2C6 SDA/SCL pinmux
Date: Mon, 25 Jan 2021 15:38:49 +0100 [thread overview]
Message-ID: <06748341-211c-c956-7ac2-d85ca0b582e2@foss.st.com> (raw)
In-Reply-To: <20201223110757.126937-1-jagan@amarulasolutions.com>
Hi,
On 12/23/20 12:07 PM, Jagan Teki wrote:
> Add SDA/SCL pinmux lines for I2C6 on STM32MP1.
>
> This support adds both in default and sleep states.
>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---
> arch/arm/boot/dts/stm32mp15-pinctrl.dtsi | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/arch/arm/boot/dts/stm32mp15-pinctrl.dtsi b/arch/arm/boot/dts/stm32mp15-pinctrl.dtsi
> index 20a59e8f7a33..2036c1d0d798 100644
> --- a/arch/arm/boot/dts/stm32mp15-pinctrl.dtsi
> +++ b/arch/arm/boot/dts/stm32mp15-pinctrl.dtsi
> @@ -2018,6 +2018,23 @@ pins {
> };
> };
>
> + i2c6_pins_a: i2c6-0 {
> + pins {
> + pinmux = <STM32_PINMUX('Z', 6, AF2)>, /* I2C6_SCL */
> + <STM32_PINMUX('Z', 7, AF2)>; /* I2C6_SDA */
> + bias-disable;
> + drive-open-drain;
> + slew-rate = <0>;
> + };
> + };
> +
> + i2c6_sleep_pins_a: i2c6-sleep-0 {
> + pins {
> + pinmux = <STM32_PINMUX('Z', 6, ANALOG)>, /* I2C6_SCL */
> + <STM32_PINMUX('Z', 7, ANALOG)>; /* I2C6_SDA */
> + };
> + };
> +
> spi1_pins_a: spi1-0 {
> pins1 {
> pinmux = <STM32_PINMUX('Z', 0, AF5)>, /* SPI1_SCK */
>
Applied on stm32-next.
Thanks.
Alex
prev parent reply other threads:[~2021-01-26 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 11:07 Jagan Teki
2021-01-25 14:38 ` 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=06748341-211c-c956-7ac2-d85ca0b582e2@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=jagan@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®