From: Matthias Brugger <matthias.bgg@gmail.com>
To: Frank Wunderlich <linux@fw-web.de>,
linux-mediatek@lists.infradead.org,
Chun-Kuang Hu <chunkuang.hu@kernel.org>
Cc: Frank Wunderlich <frank-w@public-files.de>,
Chunfeng Yun <chunfeng.yun@mediatek.com>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Ryder Lee <ryder.lee@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
Alex Ryabchenko <d3adme4t@gmail.com>
Subject: Re: [PATCH v6 4/4] arm: dts: mt7623: add lima related regulator
Date: Wed, 9 Sep 2020 11:42:43 +0200 [thread overview]
Message-ID: <b893cbdb-2011-88a4-dd57-3ea82cde08d8@gmail.com> (raw)
In-Reply-To: <20200904110002.88966-5-linux@fw-web.de>
On 04/09/2020 13:00, Frank Wunderlich wrote:
> From: Alex Ryabchenko <d3adme4t@gmail.com>
>
> GPU needs additional regulator, add it to devicetree of bpi-r2
>
> Signed-off-by: Alex Ryabchenko <d3adme4t@gmail.com>
> Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
Applied to v5.9-next/dts32
Thanks!
> ---
> arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts b/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
> index f41f221e56ca..826912545ef1 100644
> --- a/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
> +++ b/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
> @@ -79,6 +79,13 @@ reg_5v: regulator-5v {
> regulator-always-on;
> };
>
> + reg_vgpu: fixedregulator@0 {
> + compatible = "regulator-fixed";
> + regulator-name = "vdd_fixed_vgpu";
> + regulator-min-microvolt = <1150000>;
> + regulator-max-microvolt = <1150000>;
> + };
> +
> gpio-keys {
> compatible = "gpio-keys";
> pinctrl-names = "default";
> @@ -283,6 +290,11 @@ &i2c1 {
> status = "okay";
> };
>
> +&mali {
> + mali-supply = <®_vgpu>;
> + status = "okay";
> +};
> +
> &mmc0 {
> pinctrl-names = "default", "state_uhs";
> pinctrl-0 = <&mmc0_pins_default>;
> @@ -402,4 +414,3 @@ &u3phy1 {
> &u3phy2 {
> status = "okay";
> };
> -
>
prev parent reply other threads:[~2020-09-09 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 10:59 [PATCH v6 0/4] make hdmi work on bananapi-r2 Frank Wunderlich
2020-09-04 10:59 ` [PATCH v6 1/4] drm/mediatek: disable tmds on mt2701 Frank Wunderlich
2020-09-14 22:09 ` Chun-Kuang Hu
2020-09-04 11:00 ` [PATCH v6 2/4] arm: dts: mt7623: move display nodes to separate mt7623n.dtsi Frank Wunderlich
2020-09-09 9:42 ` Matthias Brugger
2020-09-04 11:00 ` [PATCH v6 3/4] arm: dts: mt7623: add display subsystem related device nodes Frank Wunderlich
2020-09-09 9:42 ` Matthias Brugger
2020-09-04 11:00 ` [PATCH v6 4/4] arm: dts: mt7623: add lima related regulator Frank Wunderlich
2020-09-09 9:42 ` Matthias Brugger [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=b893cbdb-2011-88a4-dd57-3ea82cde08d8@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=chunfeng.yun@mediatek.com \
--cc=chunkuang.hu@kernel.org \
--cc=d3adme4t@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=frank-w@public-files.de \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@fw-web.de \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.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).