Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Chen-Yu Tsai <wenst@chromium.org>,
	Matthias Brugger <matthias.bgg@gmail.com>
Cc: linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: mediatek: mt8188-geralt: Add MT6319 PMIC
Date: Tue, 7 Jul 2026 13:05:17 +0200	[thread overview]
Message-ID: <176dd24c-c3cf-4ab9-8497-594ed65d10ec@collabora.com> (raw)
In-Reply-To: <20260707104427.3409290-1-wenst@chromium.org>

On 7/7/26 12:44, Chen-Yu Tsai wrote:
> The Geralt design uses a MT6319 PMIC to power the big cores and LPDDR4X
> DRAM.
> 
> Add a device node for it and hook up all the supplies.
> 
> This change requires a firmware fix for the SPMI bus to read back
> correctly. The required firmware version is 15842.175.0. This is
> included in ChromeOS releases R150-16700.22.0 (available in Beta
> channel as of writing or stable channel in mid-July) or
> R151-16721.0.0 and later.
> 
> Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>

This is a big problem then.

I take it as if the firmware fix is not in place, probing the CPU power supplies
will fail, with all the consequences.

This means that with this, we're breaking all Geralt machines with older firmware,
which is not acceptable...

...so this needs a different solution, or strong reasons to make me understand that
I'm wrong, if I'm wrong.

Cheers,
Angelo

> ---
>   .../boot/dts/mediatek/mt8188-geralt.dtsi      | 66 +++++++++++++++++++
>   1 file changed, 66 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/mediatek/mt8188-geralt.dtsi b/arch/arm64/boot/dts/mediatek/mt8188-geralt.dtsi
> index f382f90c48f5..fea52c377d88 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8188-geralt.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8188-geralt.dtsi
> @@ -4,6 +4,8 @@
>    */
>   /dts-v1/;
>   #include <dt-bindings/gpio/gpio.h>
> +#include <dt-bindings/spmi/spmi.h>
> +
>   #include "mt8188.dtsi"
>   #include "mt6359.dtsi"
>   
> @@ -241,6 +243,14 @@ &cpu5 {
>   	cpu-supply = <&mt6359_vcore_buck_reg>;
>   };
>   
> +&cpu6 {
> +	cpu-supply = <&mt6319_buck1>;
> +};
> +
> +&cpu7 {
> +	cpu-supply = <&mt6319_buck1>;
> +};
> +
>   /*
>    * Geralt is the reference design and doesn't have target TDP.
>    * Ciri is (currently) the only device following Geralt, and its
> @@ -1156,6 +1166,14 @@ pins-bus {
>   		};
>   	};
>   
> +	spmi_pins: spmi-pins {
> +		pins-bus {
> +			pinmux = <PINMUX_GPIO175__FUNC_B0_SPMI_M_SCL>,
> +				 <PINMUX_GPIO176__FUNC_B0_SPMI_M_SDA>;
> +			bias-disable;
> +		};
> +	};
> +
>   	uart0_pins: uart0-pins {
>   		pins-bus {
>   			pinmux = <PINMUX_GPIO31__FUNC_O_UTXD0>,
> @@ -1267,6 +1285,54 @@ &spi2 {
>   	status = "okay";
>   };
>   
> +&spmi {
> +	pinctrl-names = "default";
> +	pinctrl-0 = <&spmi_pins>;
> +	#address-cells = <2>;
> +	#size-cells = <0>;
> +	status = "okay";
> +
> +	pmic@6 {
> +		compatible = "mediatek,mt6319-regulator", "mediatek,mt6315-regulator";
> +		reg = <0x6 SPMI_USID>;
> +		pvdd1-supply = <&pp4200_s5>;
> +		pvdd2-supply = <&pp4200_s5>;
> +		pvdd3-supply = <&pp4200_s5>;
> +		pvdd4-supply = <&pp4200_s5>;
> +
> +		regulators {
> +			mt6319_buck1: vbuck1 {
> +					regulator-name = "ppvar_dvdd_proc_bc";
> +					regulator-min-microvolt = <520000>;
> +					regulator-max-microvolt = <1155000>;
> +					regulator-enable-ramp-delay = <256>;
> +					regulator-allowed-modes = <0 1 2>;
> +					regulator-always-on;
> +			};
> +
> +			/* vbuck2 is ganged with vbuck1 */
> +
> +			mt6319_buck3: vbuck3 {
> +					regulator-name = "pp1125_emi_vdd2";
> +					regulator-min-microvolt = <1060000>;
> +					regulator-max-microvolt = <1170000>;
> +					regulator-enable-ramp-delay = <256>;
> +					regulator-allowed-modes = <0 1 2>;
> +					regulator-always-on;
> +			};
> +
> +			mt6319_buck4: vbuck4 {
> +					regulator-name = "pp0600_emi_vddq";
> +					regulator-min-microvolt = <570000>;
> +					regulator-max-microvolt = <650000>;
> +					regulator-enable-ramp-delay = <256>;
> +					regulator-allowed-modes = <0 1 2>;
> +					regulator-always-on;
> +			};
> +		};
> +	};
> +};
> +
>   &uart0 {
>   	pinctrl-names = "default";
>   	pinctrl-0 = <&uart0_pins>;



  reply	other threads:[~2026-07-07 11:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 10:44 [PATCH] arm64: dts: mediatek: mt8188-geralt: Add MT6319 PMIC Chen-Yu Tsai
2026-07-07 11:05 ` AngeloGioacchino Del Regno [this message]
2026-07-07 11:08   ` Chen-Yu Tsai
2026-07-07 11:24     ` AngeloGioacchino Del Regno
2026-07-08  4:25       ` Chen-Yu Tsai
2026-07-08  8:02         ` AngeloGioacchino Del Regno
2026-07-08  8:15           ` Chen-Yu Tsai

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=176dd24c-c3cf-4ab9-8497-594ed65d10ec@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=wenst@chromium.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