From: Vyacheslav Bocharov <adeep@lexina.in>
To: Neil Armstrong <narmstrong@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH v2 3/4] arm64: meson: update SDIO voltage in dts for JetHub D1
Date: Sat, 26 Mar 2022 10:51:09 +0300 [thread overview]
Message-ID: <20220326075110.1462301-4-adeep@lexina.in> (raw)
In-Reply-To: <20220326075110.1462301-1-adeep@lexina.in>
Fix the dts to match board's reference design:
- update vddio_boot regulator to 3.3v (Wi-Fi SDIO module)
- add vccq_1v8 regulator with 1.8v for eMMC SDIO
In the first revision of JetHub D1 the vccq_1v8 regulator was 3.3v.
All installed eMMC modules were tested to work in HS200 mode at 3.3v
supply voltage. In the next revisions of the board eMMC will be
powered with 1.8v according to the standard.
Signed-off-by: Vyacheslav Bocharov <adeep@lexina.in>
---
.../dts/amlogic/meson-axg-jethome-jethub-j100.dts | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg-jethome-jethub-j100.dts b/arch/arm64/boot/dts/amlogic/meson-axg-jethome-jethub-j100.dts
index 66c1eeba8f48..e52abffdf8cf 100644
--- a/arch/arm64/boot/dts/amlogic/meson-axg-jethome-jethub-j100.dts
+++ b/arch/arm64/boot/dts/amlogic/meson-axg-jethome-jethub-j100.dts
@@ -81,6 +81,15 @@ vddio_ao18: regulator-vddio_ao18 {
vddio_boot: regulator-vddio_boot {
compatible = "regulator-fixed";
regulator-name = "VDDIO_BOOT";
+ regulator-min-microvolt = <3300000>;
+ regulator-max-microvolt = <3300000>;
+ vin-supply = <&vddao_3v3>;
+ regulator-always-on;
+ };
+
+ vccq_1v8: regulator-vccq_1v8 {
+ compatible = "regulator-fixed";
+ regulator-name = "VCCQ_1V8";
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <1800000>;
vin-supply = <&vddao_3v3>;
@@ -282,7 +291,7 @@ &sd_emmc_c {
mmc-pwrseq = <&emmc_pwrseq>;
vmmc-supply = <&vcc_3v3>;
- vqmmc-supply = <&vddio_boot>;
+ vqmmc-supply = <&vccq_1v8>;
};
/* UART Bluetooth */
--
2.30.2
next prev parent reply other threads:[~2022-03-26 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 7:51 [PATCH v2 0/4] arm64: meson: update dts for JetHub devices Vyacheslav Bocharov
2022-03-26 7:51 ` [PATCH v2 1/4] arm64: meson: add dts bluetooth node for JetHub H1 Vyacheslav Bocharov
2022-03-26 7:51 ` [PATCH v2 2/4] arm64: meson: dts: update serial alias in dts for JetHub D1 Vyacheslav Bocharov
2022-03-26 7:51 ` Vyacheslav Bocharov [this message]
2022-03-26 7:51 ` [PATCH v2 4/4] arm64: meson: update WiFi SDIO " Vyacheslav Bocharov
2022-04-04 7:55 ` [PATCH v2 0/4] arm64: meson: update dts for JetHub devices Neil Armstrong
2022-04-04 8:01 ` Neil Armstrong
2022-04-04 10:39 ` Vyacheslav
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=20220326075110.1462301-4-adeep@lexina.in \
--to=adeep@lexina.in \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.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).