From: Alexandre Torgue <alexandre.torgue@st.com>
To: Benjamin Gaignard <benjamin.gaignard@st.com>,
<mcoquelin.stm32@gmail.com>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>
Cc: <linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: stm32: Add power-supply for RGB panel on stm32429i-eval
Date: Thu, 9 Jan 2020 10:46:51 +0100 [thread overview]
Message-ID: <2af148e9-c67c-0654-716b-1e65a77510b7@st.com> (raw)
In-Reply-To: <20200108132647.26131-1-benjamin.gaignard@st.com>
Hi
On 1/8/20 2:26 PM, Benjamin Gaignard wrote:
> Add a fixed regulator and use it as power supply for RBG panel.
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> ---
> arch/arm/boot/dts/stm32429i-eval.dts | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm/boot/dts/stm32429i-eval.dts b/arch/arm/boot/dts/stm32429i-eval.dts
> index 58288aa53fee..c27fa355e5ab 100644
> --- a/arch/arm/boot/dts/stm32429i-eval.dts
> +++ b/arch/arm/boot/dts/stm32429i-eval.dts
> @@ -95,6 +95,13 @@
> regulator-max-microvolt = <3300000>;
> };
>
> + vdd_panel: vdd-panel {
> + compatible = "regulator-fixed";
> + regulator-name = "vdd_panel";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + };
> +
> leds {
> compatible = "gpio-leds";
> green {
> @@ -138,6 +145,7 @@
>
> panel_rgb: panel-rgb {
> compatible = "ampire,am-480272h3tmqw-t01h";
> + power-supply = <&vdd_panel>;
> status = "okay";
> port {
> panel_in_rgb: endpoint {
>
Applied on stm32-next.
Thanks
Alex
prev parent reply other threads:[~2020-01-09 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 13:26 [PATCH] ARM: dts: stm32: Add power-supply for RGB panel on stm32429i-eval Benjamin Gaignard
2020-01-08 13:26 ` [PATCH] ARM: dts: stm32: Add power-supply for DSI panel on stm32f469-disco Benjamin Gaignard
2020-01-09 9:47 ` Alexandre Torgue
2020-01-09 9:46 ` 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=2af148e9-c67c-0654-716b-1e65a77510b7@st.com \
--to=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.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).