Received-SPF: pass (google.com: domain of linux-kernel+bounces-159054-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Message-ID: <35e37395-c6d9-42ef-839c-bac47b50f3bf@ti.com>
Date: Thu, 25 Apr 2024 14:03:36 -0500
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH v8 1/4] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs
To: Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>
CC: Nishanth Menon <nm@ti.com>, Bjorn Andersson <andersson@kernel.org>,
        Philipp Zabel <p.zabel@pengutronix.de>, <devicetree@vger.kernel.org>,
        Conor
 Dooley <conor+dt@kernel.org>, Hari Nagalla <hnagalla@ti.com>,
        <linux-kernel@vger.kernel.org>, Tero Kristo <kristo@kernel.org>,
        Krzysztof
 Kozlowski <krzk+dt@kernel.org>,
        <linux-remoteproc@vger.kernel.org>,
        Vignesh
 Raghavendra <vigneshr@ti.com>,
        <linux-arm-kernel@lists.infradead.org>,
        Mathieu Poirier <mathieu.poirier@linaro.org>
References: <20240424190612.17349-1-afd@ti.com>
 <20240424190612.17349-2-afd@ti.com>
 <171399099843.670532.4326365049493230346.robh@kernel.org>
 <20240425-herself-brigade-5b6b53dc5133@spud>
Content-Language: en-US
From: Andrew Davis <afd@ti.com>
In-Reply-To: <20240425-herself-brigade-5b6b53dc5133@spud>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit

On 4/25/24 12:15 PM, Conor Dooley wrote:
> On Wed, Apr 24, 2024 at 03:36:39PM -0500, Rob Herring wrote:
>>
>> On Wed, 24 Apr 2024 14:06:09 -0500, Andrew Davis wrote:
>>> From: Hari Nagalla <hnagalla@ti.com>
>>>
>>> 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@collabora.com>
>>> Signed-off-by: Hari Nagalla <hnagalla@ti.com>
>>> Signed-off-by: Andrew Davis <afd@ti.com>
>>> ---
>>>   .../bindings/remoteproc/ti,k3-m4f-rproc.yaml  | 126 ++++++++++++++++++
>>>   1 file changed, 126 insertions(+)
>>>   create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml
>>>
>>
>> My bot found errors running 'make dt_binding_check' on your patch:
>>
>> yamllint warnings/errors:
>>
>> dtschema/dtc warnings/errors:
>>
>>
>> doc reference errors (make refcheckdocs):
>> Warning: Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml references a file that doesn't exist: Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml
>> Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml: Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml
> 
> The file is now in dt-schema:
> https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/reserved-memory/reserved-memory.yaml

So should I use "reserved-memory/reserved-memory.yaml" here, or just
drop this line completely?

Andrew