From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-185.mta0.migadu.com (out-185.mta0.migadu.com [91.218.175.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 92DB23DCDA2 for ; Wed, 10 Jun 2026 10:06:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.185 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781085968; cv=none; b=bN8HfRIByjbGCf1Id0Rb+00F+aErRg6yi0Go/G53DSVlm0UIrLD1KZlx1O81q5Xu7JDhwrwEOXA/rDBfyMuYqykx9sl42R74nHJZMICXZ6BnLWoW2IDvVqxPN1pa2cgjZDtMjsfr7+Y6nWf7fqUQZnjPJ66NsWUOiR9evT41q9w= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781085968; c=relaxed/simple; bh=nDKru+A/5+2b/+LLwoootxfndMCqwvHDdol8mHMjvc0=; h=Mime-Version:Content-Type:Date:Message-Id:Cc:Subject:From:To: References:In-Reply-To; b=WSqTa5EwopwqbnmET6D1YRjzytOX6kk77f7hT/U1l+WwyOfNO61UQnmbtXb5eVRIwllcaRGX7wPTUf2tTW274P/BSGft5QZcxg99BQEnqR43CgL86QfcDr+cINmRDC2SHO3XJZ9EonSe+BQJp/LSCiCJUbSrFlormoZJlKZ1vFg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=cknow-tech.com; spf=pass smtp.mailfrom=cknow-tech.com; dkim=pass (2048-bit key) header.d=cknow-tech.com header.i=@cknow-tech.com header.b=X3cX35lj; arc=none smtp.client-ip=91.218.175.185 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=cknow-tech.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=cknow-tech.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=cknow-tech.com header.i=@cknow-tech.com header.b="X3cX35lj" Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cknow-tech.com; s=key1; t=1781085953; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YXhOcqMPHO+S5QqlHxh7fMeK781ZP72bMnS5EH8zaug=; b=X3cX35ljKdPrn8ghjGraHP1nRfUjKOzodTDZBQC8Bodbl4K5BZ3SeQCEUQYnIQHXomWMv2 GDYsnnYDG6qC9nxUOC6skm9sE/n1P6wkH55bWQZjwRr28gq4kBZemajTf/2mM0CPe52B5u 4IASRmUHKLwqpGKX38uLjYe3EMrnhDqZppAtJmbn8Ed7cp/1gIkFPaAccACARsT97Bxzcs HPydH1A3PBbFf0pU8obu+92IEPA+vLo2RX0wsIfwwIjfCjhrfZQFDAtSiiSsMaiiVXOyM+ irD1BK2deVH2yC9tmxTdbTJXa+lrr3N7jnjiUNuYuTEjOYBkP69T0tsjKXcRaA== Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Wed, 10 Jun 2026 12:05:49 +0200 Message-Id: Cc: , , , , , , , , , , , , , , , "Simon Xue" , "Finley Xiao" , "Jonas Karlman" Subject: Re: [RFC PATCH v3 0/9] accel: rocket: Add RK3568 NPU support X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: "Diederik de Haas" To: "Chaoyi Chen" , "Midgy Balon" References: <20260604135255.62682-1-midgy971@gmail.com> <3d99569e-9c3a-49d1-93fb-1335382523e9@rock-chips.com> In-Reply-To: X-Migadu-Flow: FLOW_OUT Hi, On Wed Jun 10, 2026 at 3:14 AM CEST, Chaoyi Chen wrote: > Hi Midgy, > > On 6/9/2026 7:11 PM, Midgy Balon wrote: >> Hello Chaoyi, >>=20 >> You were right - building rocket as a module fixes it. Thanks for the po= inter. >>=20 >> I rebuilt with CONFIG_DRM_ACCEL_ROCKET=3Dm (everything else the same: >> need_regulator on >> the RK3568 NPU power domain via a DOMAIN_M_R variant, domain-supply =3D >> <&vdd_npu>, and the >> regulator-always-on workaround dropped). The board now boots cleanly >> and, more importantly, >> an NPU job submit no longer hangs: I ran the test workload five times >> with no RCU stall and >> no freeze. >>=20 >> So with rocket=3Dm the need_regulator approach works on RK3568, and I'll >> keep it for v4 >> (domain-supply + need_regulator, instead of marking vdd_npu >> always-on). rocket=3Dm is the >> normal configuration anyway; my earlier hang came from building it =3Dy >> in a self-contained >> image, so it probed in the initcalls (around 2 s) and the genpd -> >> I2C-PMIC regulator >> transition ran before the system was ready. As a module it loads from >> udev much later >> (~6.8 s here), after the I2C controller and regulator core are fully up. >>=20 >> On your question of when the device-link error is printed - it is at >> power-domain >> controller probe, not at the rocket probe: >>=20 >> [ 2.700618] vdd_npu: Bringing 500000uV into 825000-825000uV >> [ 2.749637] rockchip-pm-domain fdd90000.power-management:power-cont= roller: >> Failed to create device link (0x180) with supplier 0-00= 20 for >> /power-management@fdd90000/power-controller/power-domai= n@6 >> [ 2.945955] platform fde40000.npu: Adding to iommu group 3 >> ... >> [ 6.840374] rocket: loading out-of-tree module taints kernel. >> [ 6.877647] [drm] Initialized rocket 0.0.0 for rknn on minor 0 >> [ 6.879950] rocket fde40000.npu: Rockchip NPU core 0 version: 0 >>=20 >> So the device-link to the rk809 PMIC (0-0020) fails to form at ~2.75 >> s, well before rocket >> loads at ~6.8 s. It is non-fatal here - the vdd_npu rail is brought up >> by the regulator core >> and all jobs run - and there is no "failed to get ack on domain npu" >> NoC warning this boot >> (the always-on kernel had one). The complete boot log is attached. >>=20 >> Two notes / one question: >> - This boot used fw_devlink=3Dpermissive on the command line. Is the >> "Failed to create device >> link ... supplier 0-0020" at pmdomain probe expected/benign, or is >> there a clean way to make >> it order correctly (so it also works without permissive, and a =3Dy >> build wouldn't deadlock in >> the initcalls)? > > We encountered the same issue on the RK3588 NPU before. And it was > resolved with the following patch at that time. > > https://lore.kernel.org/all/20251216055247.13150-1-rmxpzlb@gmail.com/ > > Please compare the differences in NPU pmdomain and DTS configuration > between the RK3568 and RK3588. About a month ago on #linux-rockchip we were discussing PM 'stuff': https://libera.catirclogs.org/linux-rockchip/2026-05-15#39939137; which references this paste https://paste.sr.ht/~diederik/89d9f84e22474e837b55286d213b67f03859ce2e I've since removed the DCDC_REG2 for PineTab2 and the 'fix' should likely be extended to cover all RK3566/RK3568 devices though. It's what I made at the time hoping to fix a suspend/resume issue when trying upstream TF-A. It didn't fix the issue at the time, but may still be useful/needed and I think it's what Chaoyi hinted at. Just yesterday, Jonas posted this patch which may be useful/needed too: https://lore.kernel.org/linux-rockchip/20260609154124.445182-1-jonas@kwiboo= .se/ HTH, Diederik >> - (The convolution output is still uniform zero-point / the job times >> out - that is the >> separate NPU compute-completion issue, unrelated to the power-domain >> work. Finley, that is >> the one I flagged earlier re PVTPLL/NoC.) >>=20 >> Kind regards, >> Midgy >>=20