[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <579c3ab0-8595-10f4-e257-d4c67c11dbb3@kernel.org>
Date: Thu, 3 Aug 2023 13:19:56 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Hari Nagalla <hnagalla@...com>, andersson@...nel.org,
mathieu.poirier@...aro.org, p.zabel@...gutronix.de,
martyn.welch@...labora.com
Cc: linux-remoteproc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 1/3] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs
On 01/08/2023 16:11, Hari Nagalla wrote:
> K3 AM64x SoC has a Cortex M4F subsystem in the MCU voltage domain.
> The remote processor's life cycle management and IPC mechanisms are
> similar across the R5F and M4F cores from remote processor driver
> point of view. However, there are subtle differences in image loading
> and starting the M4F subsystems.
>
> The YAML binding document provides the various node properties to be
> configured by the consumers of the M4F subsystem.
>
> Signed-off-by: Martyn Welch <martyn.welch@...labora.com>
> Signed-off-by: Hari Nagalla <hnagalla@...com>
> ---
>
> Changes since v1:
> - Spelling corrections
> - Corrected to pass DT checks
I don't think so.
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.
You missed at least DT list (maybe more), so this won't be tested by
automated tooling. Performing review on untested code might be a waste
of time, thus I will skip this patch entirely till you follow the
process allowing the patch to be tested.
Please kindly resend and include all necessary To/Cc entries.
Best regards,
Krzysztof
Powered by blists - more mailing lists