From: Jiaxing Hu <gahing@gahingwoo.com>
To: chaoyi.chen@rock-chips.com, royalnet026@gmail.com,
heiko@sntech.de, tomeu@tomeuvizoso.net, robin.murphy@arm.com,
diederik@cknow-tech.com
Cc: alchark@flipper.net, linux-rockchip@lists.infradead.org,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Jiaxing Hu <gahing@gahingwoo.com>
Subject: Re: [RFC PATCH v6 7/9] accel/rocket: add RK3576 NPU (RKNN) support
Date: Mon, 10 Aug 2026 22:47:28 +1200 [thread overview]
Message-ID: <20260810104728.1214233-1-gahing@gahingwoo.com> (raw)
In-Reply-To: <20260808123926.23903-1-royalnet026@gmail.com>
Hi Igor,
> One item outlives it, because it is not part of the poll machinery. In
> rocket_core_init(), the new multi-power-domain attach returns without
> unwinding rocket_job_init():
You are right, and the path immediately above it is the model, as you
say. RK3576 still needs the attach in v7, so the shape does survive the
rewrite, and v7 unwinds rocket_job_init() on that return.
> the commit message says nothing changes for RK3588, but struct
> rocket_core's clks[] grows from 4 to 6 there while the two extra names
> only arrive in 7/9
Moved rather than explained: the array grows in the patch that adds the
two names, so the RK3588 patch really does change nothing for RK3588.
The poll is gone in v7 entirely, not reduced. With the TASK_CON fix the
interrupt retires every job, so there is nothing for a fallback to fall
back to, and a fallback that never runs is a fallback nobody tests. The
job_lock move goes out on its own with a Fixes tag rather than riding in
a feature series, so it can be picked up on its own timeline.
> I would rather send you results than a tag that covers less than it
> looks like it does.
So would I, and thank you for putting it that way. Probe, multi-task
jobs, all three cores in parallel, a forced timeout and reset, and
runtime-PM cycling against a bit-exact oracle is more coverage than any
tag I could ask you for. I will send v7 to you directly when it goes
out.
Jiaxing
next prev parent reply other threads:[~2026-08-10 10:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 6:34 [RFC PATCH v6 0/9] accel/rocket: RK3576 NPU (RKNN) enablement Jiaxing Hu
2026-08-06 6:34 ` [RFC PATCH v6 1/9] dt-bindings: npu: rockchip: add rockchip,rk3576-rknn-core Jiaxing Hu
2026-08-06 6:34 ` [RFC PATCH v6 2/9] dt-bindings: power: rockchip: allow resets in a power domain node Jiaxing Hu
2026-08-06 6:34 ` [RFC PATCH v6 3/9] dt-bindings: iommu: rockchip: allow the RK3576 NPU MMU clock set Jiaxing Hu
2026-08-06 9:23 ` Diederik de Haas
2026-08-06 9:55 ` Jiaxing Hu
2026-08-06 11:29 ` Diederik de Haas
2026-08-06 6:34 ` [RFC PATCH v6 4/9] pmdomain/rockchip: add optional per-domain power-on settle delay Jiaxing Hu
2026-08-06 6:34 ` [RFC PATCH v6 5/9] pmdomain/rockchip: cycle optional power-domain resets on power-on Jiaxing Hu
2026-08-06 6:34 ` [RFC PATCH v6 6/9] accel/rocket: select the per-core clock and reset counts from match data Jiaxing Hu
2026-08-07 8:10 ` Diederik de Haas
2026-08-06 6:34 ` [RFC PATCH v6 7/9] accel/rocket: add RK3576 NPU (RKNN) support Jiaxing Hu
2026-08-07 8:48 ` Diederik de Haas
2026-08-07 12:55 ` Robin Murphy
2026-08-07 13:32 ` Diederik de Haas
2026-08-07 14:24 ` Robin Murphy
2026-08-07 21:16 ` Jiaxing Hu
2026-08-08 12:39 ` Igor Paunovic
2026-08-10 10:47 ` Jiaxing Hu [this message]
2026-08-10 1:31 ` Chaoyi Chen
2026-08-10 10:47 ` Jiaxing Hu
2026-08-06 6:34 ` [RFC PATCH v6 8/9] arm64: dts: rockchip: rk3576: add NPU (RKNN) nodes Jiaxing Hu
2026-08-06 6:34 ` [RFC PATCH v6 9/9] arm64: dts: rockchip: rk3576-rock-4d: enable NPU Jiaxing Hu
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=20260810104728.1214233-1-gahing@gahingwoo.com \
--to=gahing@gahingwoo.com \
--cc=alchark@flipper.net \
--cc=chaoyi.chen@rock-chips.com \
--cc=diederik@cknow-tech.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robin.murphy@arm.com \
--cc=royalnet026@gmail.com \
--cc=tomeu@tomeuvizoso.net \
/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;
as well as URLs for NNTP newsgroup(s).