From: Hari Nagalla <hnagalla@ti.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<andersson@kernel.org>, <mathieu.poirier@linaro.org>,
<p.zabel@pengutronix.de>, <martyn.welch@collabora.com>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>
Cc: <linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v6 1/4] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs
Date: Wed, 13 Sep 2023 08:59:26 -0500 [thread overview]
Message-ID: <b8305681-9fa5-e506-b8c7-03338b5ed4d8@ti.com> (raw)
In-Reply-To: <052be57d-4081-43ca-6c9f-9afedb030a58@linaro.org>
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..
$ 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@ti.com>
>> + - Mathieu Poirier<mathieu.poirier@linaro.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.
I will look into the other comments for the 'ti,k3-m4f-rproc.yaml'
binding doc.
Thanks
next prev parent reply other threads:[~2023-09-13 13:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 11:16 [PATCH v6 0/4] TI K3 M4F support on AM64x and AM62x SoCs Hari Nagalla
2023-09-13 11:16 ` [PATCH v6 1/4] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs Hari Nagalla
2023-09-13 11:32 ` Krzysztof Kozlowski
2023-09-13 13:59 ` Hari Nagalla [this message]
2023-09-13 15:43 ` Krzysztof Kozlowski
2023-09-13 12:36 ` Rob Herring
2023-09-13 15:54 ` Krzysztof Kozlowski
2023-09-14 15:35 ` Rob Herring
2023-09-13 11:16 ` [PATCH v6 2/4] remoteproc: k3: Split out data structures common with M4 driver Hari Nagalla
2023-09-13 11:34 ` Krzysztof Kozlowski
2023-09-13 11:16 ` [PATCH v6 3/4] remoteproc: k3: Split out functions " Hari Nagalla
2023-09-13 11:37 ` Krzysztof Kozlowski
2023-09-13 11:16 ` [PATCH v6 4/4] remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem Hari Nagalla
2023-09-13 11:34 ` Krzysztof Kozlowski
2023-09-13 11:36 ` Krzysztof Kozlowski
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=b8305681-9fa5-e506-b8c7-03338b5ed4d8@ti.com \
--to=hnagalla@ti.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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=martyn.welch@collabora.com \
--cc=mathieu.poirier@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox