From: Jiaxing Hu <gahing@gahingwoo.com>
To: robh@kernel.org
Cc: krzysztof.kozlowski@oss.qualcomm.com, conor+dt@kernel.org,
tomeu@tomeuvizoso.net, heiko@sntech.de,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 04/12] dt-bindings: npu: rockchip: add rockchip,rk3576-rknn-core
Date: Thu, 20 Aug 2026 22:16:35 +1200 [thread overview]
Message-ID: <20260820101635.752920-1-gahing@gahingwoo.com> (raw)
In-Reply-To: <178709455518.1014304.1443906758035976924.robh@kernel.org>
Hi Rob,
Taking the last paragraph first, since that is the actionable one.
In v9 the dependency will be in the patch itself, as a git note that
format-patch carries below the ---, rather than only in the cover letter where
it is now. It says the patch touches only Documentation and applies to
v7.2 on its own, and that the series it belongs to is based on next-20260814 plus
Igor Paunovic's "[PATCH v2] accel/rocket: request the core clocks by name",
which the driver patches need and this one does not.
https://lore.kernel.org/linux-rockchip/20260729130743.128876-1-royalnet026@gmail.com/
I re-ran dt_binding_check after your mail, on the three bindings this series
touches, with dtschema 2026.6, which is the current release on PyPI,
and yamllint 1.38.0.
npu/rockchip,rk3588-rknn-core.yaml clean
power/rockchip,power-controller.yaml clean
iommu/rockchip,iommu.yaml clean
None of the three reports in your mail is in a file this patch touches. The
unresolvable reference is in mfd/qcom,spmi-pmic.yaml, and the refcheckdocs
hits are in two translations and arch/arm/xen/enlighten.c. I mention it only
so it is clear I read them rather than assumed, not to argue the bot was
wrong to print them.
v9 is not posted yet, so please read the note as what it will carry and not as
done. I am holding it because v8 drew three reviewers within a day of going out
and I would rather collect the rest of that than reset the thread. Say the word
if you would prefer the respin now and I will send it.
Regards,
Jiaxing
next prev parent reply other threads:[~2026-08-20 7:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 11:35 [PATCH v8 00/12] accel/rocket: RK3576 NPU (RKNN) enablement Jiaxing Hu
2026-08-17 11:35 ` [PATCH v8 01/12] accel/rocket: take the completion register writes under job_lock Jiaxing Hu
2026-08-17 11:35 ` [PATCH v8 02/12] accel/rocket: wait for a running IRQ handler before resetting a core Jiaxing Hu
2026-08-17 12:56 ` Igor Paunovic
2026-08-17 11:35 ` [PATCH v8 03/12] accel/rocket: factor the completion tail out of the IRQ handler Jiaxing Hu
2026-08-17 12:51 ` Igor Paunovic
2026-08-17 11:35 ` [PATCH v8 04/12] dt-bindings: npu: rockchip: add rockchip,rk3576-rknn-core Jiaxing Hu
2026-08-18 23:09 ` Rob Herring (Arm)
2026-08-20 7:47 ` Krzysztof Kozlowski
2026-08-20 10:16 ` Jiaxing Hu [this message]
2026-08-17 11:35 ` [PATCH v8 05/12] dt-bindings: power: rockchip: allow resets in a power domain node Jiaxing Hu
2026-08-17 11:35 ` [PATCH v8 06/12] dt-bindings: iommu: rockchip: describe the RK3576 NPU MMU Jiaxing Hu
2026-08-17 11:35 ` [PATCH v8 07/12] pmdomain/rockchip: add optional per-domain power-on settle delay Jiaxing Hu
2026-08-17 11:35 ` [PATCH v8 08/12] pmdomain/rockchip: cycle optional power-domain resets on power-on Jiaxing Hu
2026-08-17 11:36 ` [PATCH v8 09/12] accel/rocket: select the per-core clock and reset counts from match data Jiaxing Hu
2026-08-17 11:36 ` [PATCH v8 10/12] accel/rocket: add RK3576 NPU (RKNN) support Jiaxing Hu
2026-08-18 8:59 ` Uwe Kleine-König
2026-08-17 11:36 ` [PATCH v8 11/12] arm64: dts: rockchip: rk3576: add NPU (RKNN) nodes Jiaxing Hu
2026-08-17 11:36 ` [PATCH v8 12/12] 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=20260820101635.752920-1-gahing@gahingwoo.com \
--to=gahing@gahingwoo.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--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