[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <448acb0f-fa4d-45f1-83c1-7146cda9fc25@pardini.net>
Date: Wed, 31 Dec 2025 11:47:58 +0100
From: Ricardo Pardini <ricardo@...dini.net>
To: Jimmy Hon <honyuenkwun@...il.com>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Heiko Stuebner <heiko@...ech.de>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
nicolas.frattaroli@...labora.com
Subject: Re: [PATCH 0/3] arm64: dts: rockchip: Enable the NPU on some rk3588
boards
Hi Jimmy,
>> This series enables the NPU on a few Rockchip rk3588 boards.
>> In every case here, the required regulator was already described.
> Now that the pd_npu has defined the dependency to the vdd_npu_s0,
> shouldn't the regulator-always-on be removed from the regulator? When
> the Rock5B enabled the NPU, it didn't define the regulator with always
> on. [1]
>
> More specifically, the commit message for the introduction of the
> pd_npu label mentions how the regulator no longer needs to be always
> on. [2]
>
> [1] https://lore.kernel.org/linux-rockchip/20250721-6-10-rocket-v9-10-77ebd484941e@tomeuvizoso.net/
> [2] https://lore.kernel.org/linux-rockchip/20250721-6-10-rocket-v9-7-77ebd484941e@tomeuvizoso.net/
Nice, I overlooked that. I'll send a v2 removing `regulator-always-on;`
from the regulator.
And maybe a separate series removing it from the the other NPU-enabled
boards that still have it?
Thanks,
Ricardo
Powered by blists - more mailing lists