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: <0f92b568-399e-4bd8-84f7-088abe9dbe84@linaro.org>
Date:   Wed, 13 Sep 2023 17:43:18 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Hari Nagalla <hnagalla@...com>, andersson@...nel.org,
        mathieu.poirier@...aro.org, p.zabel@...gutronix.de,
        martyn.welch@...labora.com, robh+dt@...nel.org,
        krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org
Cc:     linux-remoteproc@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v6 1/4] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs

On 13/09/2023 15:59, Hari Nagalla wrote:
> On 9/13/23 06:32, Krzysztof Kozlowski wrote:
>>>   - 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
>> Hm, why none? There were errors in the binding to which you did not
>> respond. Did you just ignore them?
>>
> I do not see any errors in my builds. Am i missing something? Please 
> excuse my lack of knowledge here. Thought the bot errors were outside of 
> the patch submitted 
> (Documentation/devicetree/bindings/dma/stericsson,dma40.yaml). 
> Appreciate your kind inputs..

I would expect then some confirmation that errors can be ignored.
Instead report was left just unanswered.

> 
> $ make -j`nproc` ARCH=arm64 V=1 CROSS_COMPILE=aarch64-none-linux-gnu- 
> DT_CHEKCER_FLAGS=-m dt_binding_check 
> DT_SCHEMA_FILES=Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml
> make --no-print-directory -C /home/a0868345/temp/linux-next \
> -f /home/a0868345/temp/linux-next/Makefile dt_binding_check
> make -f ./scripts/Makefile.build obj=scripts/basic
> make -f ./scripts/Makefile.build obj=scripts/dtc
> make -f ./scripts/Makefile.build obj=Documentation/devicetree/bindings
> # LINT    Documentation/devicetree/bindings
>    (find ./Documentation/devicetree/bindings \( -name '*.yaml' ! -name 
> 'processed-schema*' \) | grep -F -e 
> "Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml" | 
> xargs -n200 -P$(nproc) /home/a0868345/.local/bin/yamllint -f parsable -c 
> ./Documentation/devicetree/bindings/.yamllint >&2) || true
> # DTEX 
> Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.example.dts
>    dt-extract-example 
> Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml > 
> Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.example.dts
> # CHKDT   Documentation/devicetree/bindings/processed-schema.json
>    (find ./Documentation/devicetree/bindings \( -name '*.yaml' ! -name 
> 'processed-schema*' \) | grep -F -e 
> "Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml" | 
> xargs -n200 -P$(nproc) dt-doc-validate -u 
> ./Documentation/devicetree/bindings) || true
> # SCHEMA  Documentation/devicetree/bindings/processed-schema.json
>    f=$(mktemp) ; find ./Documentation/devicetree/bindings \( -name 
> '*.yaml' ! -name 'processed-schema*' \) > $f ; dt-mk-schema -j  @$f > 
> Documentation/devicetree/bindings/processed-schema.json ; rm -f $f
> # DTC_CHK 
> Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.example.dtb
>    gcc -E 
> -Wp,-MMD,Documentation/devicetree/bindings/remoteproc/.ti_k3-m4f-rproc.example.dtb.d.pre.tmp 
> -nostdinc -I./scripts/dtc/include-prefixes -undef -D__DTS__ -x 
> assembler-with-cpp -o 
> Documentation/devicetree/bindings/remoteproc/.ti_k3-m4f-rproc.example.dtb.dts.tmp 
> Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.example.dts 
> ; ./scripts/dtc/dtc -o 
> Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.example.dtb 
> -b 0 -iDocumentation/devicetree/bindings/remoteproc/ 
> -i./scripts/dtc/include-prefixes -Wno-avoid_unnecessary_addr_size 
> -Wno-graph_child_address -Wno-interrupt_provider 
> -Wno-unique_unit_address -Wunique_unit_address_if_enabled -d 
> Documentation/devicetree/bindings/remoteproc/.ti_k3-m4f-rproc.example.dtb.d.dtc.tmp 
> Documentation/devicetree/bindings/remoteproc/.ti_k3-m4f-rproc.example.dtb.dts.tmp 
> ; cat 
> Documentation/devicetree/bindings/remoteproc/.ti_k3-m4f-rproc.example.dtb.d.pre.tmp 
> Documentation/devicetree/bindings/remoteproc/.ti_k3-m4f-rproc.example.dtb.d.dtc.tmp 
>  > 
> Documentation/devicetree/bindings/remoteproc/.ti_k3-m4f-rproc.example.dtb.d 
> ; dt-validate  -u ./Documentation/devicetree/bindings -p 
> ./Documentation/devicetree/bindings/processed-schema.json 
> Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.example.dtb 
> || true
> 
> 
>  >> +# SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
>  >> +%YAML 1.2
>  >> +---
>  >> +$id:http://devicetree.org/schemas/remoteproc/ti,k3-m4f-rproc.yaml#
>  >> +$schema:http://devicetree.org/meta-schemas/core.yaml#
>  >> +
>  >> +title: TI K3 M4F processor subsystems
>  >> +
>  >> +maintainers:
>  >> +  - Hari Nagalla<hnagalla@...com>
>  >> +  - Mathieu Poirier<mathieu.poirier@...aro.org>
>  > Are you sure Mathieu has this device and is a maintainer of this device?
>  >
> Earlier, Mathieu suggested he can be the maintainer. Beagle play is 
> based on AM625 device.
> 

Sure, no problem, good for me.

Best regards,
Krzysztof