From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Olivier Moysan <olivier.moysan@foss.st.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] ARM: dts: stm32: add dfsdm & sai pin muxings on stm32mp13
Date: Fri, 22 Sep 2023 12:24:26 +0200 [thread overview]
Message-ID: <10a5fd12-1edd-96d3-caab-a1b3da969ec5@foss.st.com> (raw)
In-Reply-To: <20230919163009.203752-1-olivier.moysan@foss.st.com>
Hi Olivier
On 9/19/23 18:30, Olivier Moysan wrote:
> Add pin muxings for STM32 DFSDM and SAI audio peripherals on STM32MP13
> Disco boards expansion connector.
>
> Olivier Moysan (2):
> ARM: dts: stm32: add pins muxing for sai1 on stm32mp13
> ARM: dts: stm32: add pins muxing for dfsdm on stm32mp13
>
> arch/arm/boot/dts/st/stm32mp13-pinctrl.dtsi | 60 +++++++++++++++++++++
> 1 file changed, 60 insertions(+)
>
Why do you push only pins muxing ? I prefer to merge pins when I'm sure
that they'll be used on a board. In your case, if those pins rely on a
connector then declare this descriptor (as we did for mp15).
regards
Alex
prev parent reply other threads:[~2023-09-22 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 16:30 [PATCH 0/2] ARM: dts: stm32: add dfsdm & sai pin muxings on stm32mp13 Olivier Moysan
2023-09-19 16:30 ` [PATCH 1/2] ARM: dts: stm32: add pins muxing for sai1 " Olivier Moysan
2023-09-19 16:30 ` [PATCH 2/2] ARM: dts: stm32: add pins muxing for dfsdm " Olivier Moysan
2023-09-22 10:24 ` 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=10a5fd12-1edd-96d3-caab-a1b3da969ec5@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--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=olivier.moysan@foss.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;
as well as URLs for NNTP newsgroup(s).