From: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
<linux-kernel@vger.kernel.org>
Cc: <devicetree@vger.kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
<michael@amarulasolutions.com>,
Amarula patchwork <linux-amarula@amarulasolutions.com>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Linux-stm32] [PATCH v3 2/4] ARM: dts: stm32: add pin map for LTDC on stm32f7
Date: Fri, 9 Jun 2023 16:23:35 +0200 [thread overview]
Message-ID: <559a146a-237b-ce42-93e7-ed13cfbb209d@foss.st.com> (raw)
In-Reply-To: <20230609062050.2107143-3-dario.binacchi@amarulasolutions.com>
On 6/9/23 08:20, Dario Binacchi wrote:
> Add pin configurations for using LTDC (LCD-tft Display Controller) on
> stm32f746-disco board.
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Reviewed-by: Raphaël Gallais-Pou <raphael.gallais-pou@foss.st.com>
>
> ---
>
> Changes in v3:
> - rename ltdc-pins-a-0 to ltdc-0.
>
> arch/arm/boot/dts/stm32f7-pinctrl.dtsi | 35 ++++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
next prev parent reply other threads:[~2023-06-09 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 6:20 [PATCH v3 0/4] Add display support on the stm32f746-disco board Dario Binacchi
2023-06-09 6:20 ` [PATCH v3 1/4] ARM: dts: stm32: add ltdc support on stm32f746 MCU Dario Binacchi
2023-06-09 14:17 ` [Linux-stm32] " Raphael Gallais-Pou
2023-06-09 6:20 ` [PATCH v3 2/4] ARM: dts: stm32: add pin map for LTDC on stm32f7 Dario Binacchi
2023-06-09 14:23 ` Raphael Gallais-Pou [this message]
2023-06-09 6:20 ` [PATCH v3 3/4] ARM: dts: stm32: support display on stm32f746-disco board Dario Binacchi
2023-06-09 14:25 ` [Linux-stm32] " Raphael Gallais-Pou
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=559a146a-237b-ce42-93e7-ed13cfbb209d@foss.st.com \
--to=raphael.gallais-pou@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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=michael@amarulasolutions.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).