From: Katsuhiro Suzuki <katsuhiro@katsuster.net>
To: Heiko Stuebner <heiko@sntech.de>, linux-rockchip@lists.infradead.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH] arm64: dts: rockchip: fix IO domain voltage setting of APIO5
Date: Mon, 15 Apr 2019 18:48:06 +0900 [thread overview]
Message-ID: <5170ca5c-ac5a-d88f-6c3d-3794a5afdb30@katsuster.net> (raw)
In-Reply-To: <20190327120317.15256-1-katsuhiro@katsuster.net>
ping...
On 2019/03/27 21:03, Katsuhiro Suzuki wrote:
> This patch fixes IO domain voltage setting that is related to
> audio_gpio3d4a_ms (bit 1) of GRF_IO_VSEL.
>
> This is because RockPro64 schematics P.16 says that regulator
> supplies 3.0V power to APIO5_VDD. So audio_gpio3d4a_ms bit should
> be clear (means 3.0V). Power domain map is saying different thing
> (supplies 1.8V) but I believe P.16 is actual connectings.
>
> Signed-off-by: Katsuhiro Suzuki <katsuhiro@katsuster.net>
> Suggested-by: Robin Murphy <robin.murphy@arm.com>
> ---
> arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts b/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts
> index 791fb0ee9722..20ec7d1c25d7 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts
> @@ -508,7 +508,7 @@
> status = "okay";
>
> bt656-supply = <&vcc1v8_dvp>;
> - audio-supply = <&vcca1v8_codec>;
> + audio-supply = <&vcc_3v0>;
> sdmmc-supply = <&vcc_sdio>;
> gpio1830-supply = <&vcc_3v0>;
> };
>
next prev parent reply other threads:[~2019-04-15 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 12:03 [PATCH] arm64: dts: rockchip: fix IO domain voltage setting of APIO5 Katsuhiro Suzuki
2019-04-15 9:48 ` Katsuhiro Suzuki [this message]
2019-04-23 10:31 ` Heiko Stuebner
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=5170ca5c-ac5a-d88f-6c3d-3794a5afdb30@katsuster.net \
--to=katsuhiro@katsuster.net \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robin.murphy@arm.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).