[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4495583.CbtlEUcBR6@phil>
Date: Tue, 06 Jan 2026 19:52:56 +0100
From: Heiko Stuebner <heiko@...ech.de>
To: Quentin Schulz <quentin.schulz@...rry.de>
Cc: linux-arm-kernel@...ts.infradead.org, linux-rockchip@...ts.infradead.org,
linux-kernel@...r.kernel.org, Heiko Stuebner <heiko.stuebner@...rry.de>
Subject: Re: [PATCH 1/2] arm64: dts: rockchip: enable NPU on rk3588-tiger
Am Freitag, 28. November 2025, 11:32:17 Mitteleuropäische Normalzeit schrieb Quentin Schulz:
> Hi Heiko,
>
> On 8/12/25 10:52 AM, Heiko Stuebner wrote:
> > From: Heiko Stuebner <heiko.stuebner@...rry.de>
> >
> > Enable the NPU cores and their mmus and wire up the supply-regulator.
> > The regulator itself was already defined, but it does not need to be
> > always on - the npu can control it.
> >
> > Signed-off-by: Heiko Stuebner <heiko.stuebner@...rry.de>
>
> Reviewed-by: Quentin Schulz <quentin.schulz@...rry.de>
> Tested-by: Quentin Schulz <quentin.schulz@...rry.de>
>
> I still have the same remark about regulator-boot-on but this isn't a
> blocker per-se.
>
> The Oops I alluded to in my answer to the Jaguar patch is triggered by
> making DRM_ACCEL_ROCKET driver built-in instead of as a module. I'm not
> sure how much I will debug this on my side, I'll prolly just report this
> on the ML in a few hours.
Just for people stumbling over this, the cause is the pm-domains
being on on boot and the iommu after probing disabling the domain.
See discussion in
https://lore.kernel.org/linux-rockchip/20251216055247.13150-1-rmxpzlb@gmail.com/
Powered by blists - more mailing lists