From: Dragan Simic <dsimic@manjaro.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: linux-rockchip@lists.infradead.org, heiko@sntech.de,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, boris.brezillon@collabora.com,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH] arm64: dts: rockchip: quartzpro64: Enable the GPU
Date: Tue, 26 Mar 2024 20:57:16 +0100 [thread overview]
Message-ID: <78f5ee0cc543aa4406c15fcafa50f2e8@manjaro.org> (raw)
In-Reply-To: <jbyqey5y5ngr7mkrrmdxrwyw5ogd7rq56af6mrmhsckboanvyp@tcaav2tridos>
Hello Sebastian,
On 2024-03-26 20:54, Sebastian Reichel wrote:
> On Mon, Mar 25, 2024 at 05:19:04PM +0100, Dragan Simic wrote:
>> Following the approach used to enable the Mali GPU on the rk3588-evb1,
>> [1]
>> do the same for the Pine64 QuartzPro64, which uses nearly identical
>> hardware
>> design as the RK3588 EVB1.
>>
>> The slight disadvantage is that the regulator coupling logic requires
>> the
>> regulators to be always on, which is also noted in the comments. This
>> is
>> obviously something to be improved at some point in the future, but
>> should
>> be fine for now, especially because the QuartzPro64 isn't a
>> battery-powered
>> board, so low power consumption isn't paramount.
>>
>> [1]
>> https://lore.kernel.org/linux-rockchip/20240325153850.189128-5-sebastian.reichel@collabora.com/
>>
>> Signed-off-by: Dragan Simic <dsimic@manjaro.org>
>> ---
>
> FWIW
>
> Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Great, thanks for your review!
>> .../arm64/boot/dts/rockchip/rk3588-quartzpro64.dts | 14
>> ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3588-quartzpro64.dts
>> b/arch/arm64/boot/dts/rockchip/rk3588-quartzpro64.dts
>> index 67414d72e2b6..68d432c61ea5 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3588-quartzpro64.dts
>> +++ b/arch/arm64/boot/dts/rockchip/rk3588-quartzpro64.dts
>> @@ -285,6 +285,12 @@ &gmac0_rgmii_clk
>> status = "okay";
>> };
>>
>> +&gpu {
>> + mali-supply = <&vdd_gpu_s0>;
>> + sram-supply = <&vdd_gpu_mem_s0>;
>> + status = "okay";
>> +};
>> +
>> &i2c2 {
>> status = "okay";
>>
>> @@ -491,11 +497,15 @@ rk806_dvs3_null: dvs3-null-pins {
>> regulators {
>> vdd_gpu_s0: dcdc-reg1 {
>> regulator-name = "vdd_gpu_s0";
>> + /* regulator coupling requires always-on */
>> + regulator-always-on;
>> regulator-boot-on;
>> regulator-enable-ramp-delay = <400>;
>> regulator-min-microvolt = <550000>;
>> regulator-max-microvolt = <950000>;
>> regulator-ramp-delay = <12500>;
>> + regulator-coupled-with = <&vdd_gpu_mem_s0>;
>> + regulator-coupled-max-spread = <10000>;
>>
>> regulator-state-mem {
>> regulator-off-in-suspend;
>> @@ -545,11 +555,15 @@ regulator-state-mem {
>>
>> vdd_gpu_mem_s0: dcdc-reg5 {
>> regulator-name = "vdd_gpu_mem_s0";
>> + /* regulator coupling requires always-on */
>> + regulator-always-on;
>> regulator-boot-on;
>> regulator-enable-ramp-delay = <400>;
>> regulator-min-microvolt = <675000>;
>> regulator-max-microvolt = <950000>;
>> regulator-ramp-delay = <12500>;
>> + regulator-coupled-with = <&vdd_gpu_s0>;
>> + regulator-coupled-max-spread = <10000>;
>>
>> regulator-state-mem {
>> regulator-off-in-suspend;
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-03-26 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 16:19 [PATCH] arm64: dts: rockchip: quartzpro64: Enable the GPU Dragan Simic
2024-03-26 19:11 ` Rob Herring
2024-03-26 19:27 ` Dragan Simic
2024-03-26 19:54 ` Sebastian Reichel
2024-03-26 19:57 ` Dragan Simic [this message]
2024-03-27 10:29 ` Heiko Stübner
2024-03-27 20:28 ` Dragan Simic
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=78f5ee0cc543aa4406c15fcafa50f2e8@manjaro.org \
--to=dsimic@manjaro.org \
--cc=boris.brezillon@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.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