linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Alain Volmat <alain.volmat@foss.st.com>
Cc: <robh+dt@kernel.org>, <mcoquelin.stm32@gmail.com>,
	<krzysztof.kozlowski+dt@linaro.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<amelie.delaunay@foss.st.com>
Subject: Re: [PATCH 0/2] ARM: dts: stm32: add i2c in STM32MP13
Date: Fri, 26 Aug 2022 09:52:50 +0200	[thread overview]
Message-ID: <c8a72852-3398-fa27-bc11-07342c88fe3d@foss.st.com> (raw)
In-Reply-To: <20220721152933.3805272-1-alain.volmat@foss.st.com>

Hi Alain

On 7/21/22 17:29, Alain Volmat wrote:
> This series adds all i2c nodes for the stm32mp131 platform and
> enables i2c1 and i2c5 on the stm32mp135 discovery board.
> 
> Alain Volmat (2):
>    ARM: dts: stm32: add i2c nodes into stm32mp131.dtsi
>    ARM: dts: stm32: enable i2c1 and i2c5 on stm32mp135f-dk.dts
> 
>   arch/arm/boot/dts/stm32mp13-pinctrl.dtsi | 34 +++++++++
>   arch/arm/boot/dts/stm32mp131.dtsi        | 90 ++++++++++++++++++++++++
>   arch/arm/boot/dts/stm32mp135f-dk.dts     | 26 +++++++
>   3 files changed, 150 insertions(+)
> 

Series applied on stm32-next.

Regards
Alex

      parent reply	other threads:[~2022-08-26  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 15:29 [PATCH 0/2] ARM: dts: stm32: add i2c in STM32MP13 Alain Volmat
2022-07-21 15:29 ` [PATCH 1/2] ARM: dts: stm32: add i2c nodes into stm32mp131.dtsi Alain Volmat
2022-07-21 15:29 ` [PATCH 2/2] ARM: dts: stm32: enable i2c1 and i2c5 on stm32mp135f-dk.dts Alain Volmat
2022-08-26  7:52 ` 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=c8a72852-3398-fa27-bc11-07342c88fe3d@foss.st.com \
    --to=alexandre.torgue@foss.st.com \
    --cc=alain.volmat@foss.st.com \
    --cc=amelie.delaunay@foss.st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --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;
as well as URLs for NNTP newsgroup(s).