From: Alexandre Torgue <alexandre.torgue@st.com>
To: "Yannick Fertré" <yannick.fertre@st.com>,
"Philippe Cornu" <philippe.cornu@st.com>,
"Benjamin Gaignard" <benjamin.gaignard@st.com>,
"Vincent Abriou" <vincent.abriou@st.com>,
"David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
dri-devel@lists.freedesktop.org, 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 v1 0/5] Add supply property for DSI controller
Date: Wed, 10 Apr 2019 15:48:43 +0200 [thread overview]
Message-ID: <315b59d5-893a-607a-01e4-cf83fe1cfd86@st.com> (raw)
In-Reply-To: <1554279389-27377-1-git-send-email-yannick.fertre@st.com>
Hi Yannick
On 4/3/19 10:16 AM, Yannick Fertré wrote:
> The DSI controller needs a new property that powers its physical layer.
> Binding has been updated to documented this property.
> Device tree of stm32mp157c soc.
> Move reg18 & reg11 to stm32mp157c device tree file.
> Remove property phy-dsi-supply property to stm32mp157c-dk2.dts file.
>
> Yannick Fertré (5):
...
> ARM: dts: stm32: add phy-dsi-supply property on stm32mp157c
> ARM: dts: stm32: move fixe regulators reg11 & reg18
> ARM: dts: stm32: remove phy-dsi-supply property on stm32mp157c-dk2
> board
>
For ARM part:
Another series is currently under review: "Add support for STM32MP1
power regulators" (https://lkml.org/lkml/2019/4/8/614).
As soon I'll merge it I'll take your patches without patch
"ARM: dts: stm32: move fixe regulators reg11 & reg18" as it will be no
longer relevant.
regards
Alexandre
> .../devicetree/bindings/display/st,stm32-ltdc.txt | 3 +++
> arch/arm/boot/dts/stm32mp157c-dk2.dts | 9 ---------
> arch/arm/boot/dts/stm32mp157c-ed1.dts | 16 ----------------
> arch/arm/boot/dts/stm32mp157c.dtsi | 17 +++++++++++++++++
> drivers/gpu/drm/stm/dw_mipi_dsi-stm.c | 20 ++++++++++++++++++++
> 5 files changed, 40 insertions(+), 25 deletions(-)
>
prev parent reply other threads:[~2019-04-10 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 8:16 [PATCH v1 0/5] Add supply property for DSI controller Yannick Fertré
2019-04-03 8:16 ` [PATCH v1 1/5] dt-bindings: display: stm32: add supply property to " Yannick Fertré
2019-04-05 16:33 ` Philippe CORNU
2019-04-06 6:06 ` Rob Herring
2019-04-03 8:16 ` [PATCH v1 2/5] drm/stm: dw_mipi_dsi-stm: add support of an optional regulator Yannick Fertré
2019-04-05 16:34 ` Philippe CORNU
2019-04-03 8:16 ` [PATCH v1 3/5] ARM: dts: stm32: add phy-dsi-supply property on stm32mp157c Yannick Fertré
2019-04-03 8:16 ` [PATCH v1 4/5] ARM: dts: stm32: move fixe regulators reg11 & reg18 Yannick Fertré
2019-04-03 8:16 ` [PATCH v1 5/5] ARM: dts: stm32: remove phy-dsi-supply property on stm32mp157c-dk2 board Yannick Fertré
2019-04-10 13:48 ` 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=315b59d5-893a-607a-01e4-cf83fe1cfd86@st.com \
--to=alexandre.torgue@st.com \
--cc=airlied@linux.ie \
--cc=benjamin.gaignard@st.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.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=philippe.cornu@st.com \
--cc=robh+dt@kernel.org \
--cc=vincent.abriou@st.com \
--cc=yannick.fertre@st.com \
/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).