All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jiafei Pan <Jiafei.Pan@nxp.com>
Cc: andersson@kernel.org, mathieu.poirier@linaro.org,
	krzysztof.kozlowski@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-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Zhiqiang.Hou@nxp.com,
	mingkai.hu@nxp.com
Subject: Re: [PATCH v4 1/4] dt-bindings: remoteproc: add imx-rproc-psci
Date: Thu, 13 Aug 2026 09:51:31 +0200	[thread overview]
Message-ID: <80dfac6e-3408-4f62-887d-9da39c827dd5@kernel.org> (raw)
In-Reply-To: <20260813-imposing-blazing-gharial-fbb19c@quoll>

On 13/08/2026 09:49, Krzysztof Kozlowski wrote:
> On Wed, Aug 12, 2026 at 06:46:30PM +0800, Jiafei Pan wrote:
>> Add compatible string "fsl,imx-rproc-psci" for i.MX Cortex-A Core's
>> remoteproc support.
>>
>> Signed-off-by: Jiafei Pan <Jiafei.Pan@nxp.com>
>>
>> ---
>> Changes in v4:
>> - Updated description to describe the hardware instead of the binding
>> - Changed compatible to SoC-specific "fsl,imx93-rproc-psci" with
>>   generic fallback "fsl,imx-rproc-psci"
>> - Fixed example node name from "remoteproc-ca55-1" to "remoteproc"
> 
> You need to start using b4 to send patches or send them correctly... Why
> is this response to some other thread?
> 
>>
>> ---
>>  .../remoteproc/fsl,imx-rproc-psci.yaml        | 54 +++++++++++++++++++
>>  1 file changed, 54 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc-psci.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc-psci.yaml b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc-psci.yaml
>> new file mode 100644
>> index 000000000000..7d0d0da383a2
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc-psci.yaml
>> @@ -0,0 +1,54 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/remoteproc/fsl,imx-rproc-psci.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: NXP i.MX Cortex-A Core Remote Processor via PSCI
>> +
>> +maintainers:
>> +  - Jiafei Pan <Jiafei.Pan@nxp.com>
>> +
>> +description:
>> +  NXP i.MX SoCs integrate multiple Cortex-A cores. On certain i.MX
>> +  platforms, one or more of these cores can be offloaded to run RTOS
>> +  or bare-metal firmware as a remote processor, while the remaining
>> +  cores run Linux. The cores are powered on and off via PSCI (Power
>> +  State Coordination Interface) CPU_ON/CPU_OFF calls to the firmware.
>> +
>> +properties:
>> +  compatible:
>> +    items:
>> +      - enum:
>> +          - fsl,imx93-ca55-rproc
>> +      - const: fsl,imx-rproc-psci
> 
> Hm? So you just ignored the feedback?
> 


Ah, you just did not bother even to wait for my reply!

After three months after my review, you send reply to my comments and
IMMEDIATELY you send v4 without waiting for me to address them.

Srsly, if you have three months, then don't you think I deserve more
than 1 hour?

NAK

Best regards,
Krzysztof

  reply	other threads:[~2026-08-13  7:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11  2:39 [PATCH v3 0/4] remoteproc: add Cortex-A Core remoteproc support on i.MX platforms Jiafei Pan
2026-05-11  2:39 ` [PATCH v3 1/4] dt-bindings: remoteproc: add imx-rproc-psci Jiafei Pan
2026-05-11 22:41   ` sashiko-bot
2026-05-14 11:38   ` Krzysztof Kozlowski
2026-08-12  9:19     ` Jiafei Pan
2026-08-12 10:02       ` Krzysztof Kozlowski
2026-08-12 10:46   ` [PATCH v4 0/4] remoteproc: add Cortex-A Core remoteproc support on i.MX platforms Jiafei Pan
2026-08-12 10:46     ` [PATCH v4 1/4] dt-bindings: remoteproc: add imx-rproc-psci Jiafei Pan
2026-08-13  7:49       ` Krzysztof Kozlowski
2026-08-13  7:51         ` Krzysztof Kozlowski [this message]
2026-08-14  7:37           ` [EXT] " Jiafei Pan
2026-08-12 10:46     ` [PATCH v4 2/4] remoteproc: imx_rproc: add support for Cortex-A Core Jiafei Pan
2026-08-12 10:46     ` [PATCH v4 3/4] remoteproc: imx_rproc: add autoboot support for A-core Jiafei Pan
2026-08-12 10:46     ` [PATCH v4 4/4] arm64: dts: imx93: Cortex-A Core remoteproc device node Jiafei Pan
2026-05-11  2:39 ` [PATCH v3 2/4] remoteproc: imx_rproc: add support for Cortex-A Core Jiafei Pan
2026-05-11 23:10   ` sashiko-bot
2026-05-11  2:39 ` [PATCH v3 3/4] remoteproc: imx_rproc: add autoboot support for A-core Jiafei Pan
2026-05-12  0:00   ` sashiko-bot
2026-05-11  2:39 ` [PATCH v3 4/4] arm64: dts: imx93: Cortex-A Core remoteproc device node Jiafei Pan
2026-05-12  0:37   ` sashiko-bot
2026-05-11  7:00 ` [PATCH v3 0/4] remoteproc: add Cortex-A Core remoteproc support on i.MX platforms Peng Fan
2026-05-11 17:10   ` Mathieu Poirier

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=80dfac6e-3408-4f62-887d-9da39c827dd5@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=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.