From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jiafei Pan <Jiafei.Pan@nxp.com>,
andersson@kernel.org, mathieu.poirier@linaro.org,
peng.fan@nxp.com, Frank.Li@nxp.com, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Zhiqiang.Hou@nxp.com, mingkai.hu@nxp.com
Subject: Re: [PATCH 1/5] dt-bindings: remoteproc: add imx-rproc-psci binding
Date: Wed, 29 Apr 2026 09:05:12 +0200 [thread overview]
Message-ID: <0d67a9a7-74b5-48a3-b685-39d2fa669c78@kernel.org> (raw)
In-Reply-To: <20260428090819.17761-2-Jiafei.Pan@nxp.com>
On 28/04/2026 11:08, Jiafei Pan wrote:
> Add compatible string "fsl,imx-rproc-psci" for i.MX Cortex-A Core's
> remoteproc support.
A nit, subject: drop second/last, redundant "binding". The "dt-bindings"
prefix is already stating that these are bindings.
See also:
https://elixir.bootlin.com/linux/v6.17-rc3/source/Documentation/devicetree/bindings/submitting-patches.rst#L18
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.
Please kindly resend and include all necessary To/Cc entries.
Not doing full review - lack of usage of tools disqualifies the patchset
for review to me.
> +
> +examples:
> + - |
> + / {
> + reserved-memory {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + rtos_ca55_reserved: rtos-ca55@d0000000 {
> + reg = <0 0xd0000000 0 0x10000000>;
> + no-map;
> + };
> + };
Drop all above, I am pretty sure this will have failures, so test ALL
BINDINGS.
> +
> + remoteproc-ca55-1 {
Node names should be generic. See also an explanation and list of
examples (not exhaustive) in DT specification:
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
If you cannot find a name matching your device, please check in kernel
sources for similar cases or you can grow the spec (via pull request to
DT spec repo).
> + compatible = "fsl,imx-rproc-psci";
> + /* bitmask: 0b10, assign A55 Core 1 */
> + fsl,cpus-bits = <0x2>;
> + memory-region = <&rtos_ca55_reserved>;
> + };
> + };
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-29 7:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 9:08 [PATCH 0/5] remoteproc: add Cortex-A Core remoteproc support on i.MX platforms Jiafei Pan
2026-04-28 9:08 ` [PATCH 1/5] dt-bindings: remoteproc: add imx-rproc-psci binding Jiafei Pan
2026-04-29 7:05 ` Krzysztof Kozlowski [this message]
2026-04-28 9:08 ` [PATCH 2/5] drivers: remoteproc: imx: add support for Cortex-A Core Jiafei Pan
2026-04-29 7:05 ` Krzysztof Kozlowski
2026-04-30 6:47 ` [EXT] " Jiafei Pan
2026-04-28 9:08 ` [PATCH 3/5] drivers: remoteproc: imx: add autoboot support for A-core remoteproc Jiafei Pan
2026-04-28 13:49 ` Daniel Baluta
2026-04-30 6:22 ` Jiafei Pan
2026-04-28 9:08 ` [PATCH 4/5] arm64: dts: imx93: Cortex-A Core remoteproc device node Jiafei Pan
2026-04-29 7:07 ` Krzysztof Kozlowski
2026-04-30 6:51 ` [EXT] " Jiafei Pan
2026-04-30 8:45 ` Daniel Baluta
2026-04-28 9:08 ` [PATCH 5/5] remoteproc: imx: use device node name as processor name Jiafei Pan
2026-04-28 13:36 ` Daniel Baluta
2026-04-30 6:21 ` Jiafei Pan
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=0d67a9a7-74b5-48a3-b685-39d2fa669c78@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=Jiafei.Pan@nxp.com \
--cc=Zhiqiang.Hou@nxp.com \
--cc=andersson@kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mingkai.hu@nxp.com \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
/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