linux-kernel - Re: [PATCH v6 1/4] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48ff2a69-6eaf-78dc-0382-f0b6a6d8cddd@linaro.org>
Date:   Wed, 13 Sep 2023 17:54:37 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Rob Herring <robh@...nel.org>, Hari Nagalla <hnagalla@...com>
Cc:     linux-kernel@...r.kernel.org, martyn.welch@...labora.com,
        devicetree@...r.kernel.org, andersson@...nel.org,
        linux-remoteproc@...r.kernel.org, robh+dt@...nel.org,
        conor+dt@...nel.org, linux-arm-kernel@...ts.infradead.org,
        mathieu.poirier@...aro.org, p.zabel@...gutronix.de,
        krzysztof.kozlowski+dt@...aro.org
Subject: Re: [PATCH v6 1/4] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs

On 13/09/2023 14:36, Rob Herring wrote:
> 
> On Wed, 13 Sep 2023 06:16:41 -0500, 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
>>
>> Changes since v2:
>>  - Missed spelling correction to commit message
>>
>> Changes since v3:
>>  - Removed unnecessary descriptions and used generic memory region names
>>  - Made mboxes and memory-region optional
>>  - Removed unrelated items from examples
>>
>> Changes since v4:
>>  - Rebased to the latest kernel-next tree
>>  - Added optional sram memory region for m4f device node
>>
>> Changes since v5:
>>  - None
>>
>>  .../bindings/remoteproc/ti,k3-m4f-rproc.yaml  | 136 ++++++++++++++++++
>>  1 file changed, 136 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml
>>
> 
> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
> on your patch (DT_CHECKER_FLAGS is new in v5.13):
> 
> yamllint warnings/errors:
> 
> dtschema/dtc warnings/errors:
> /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/dma/stericsson,dma40.example.dtb: dma-controller@...c0000: sram:0: [4294967295, 4294967295] is too long
> 	from schema $id: http://devicetree.org/schemas/dma/stericsson,dma40.yaml#

This looks unrelated but it is caused by this patch. Probably by
conflicting type for 'sram'. It seems we need to make exception for
'sram' in dtschema.

Best regards,
Krzysztof