From: Rob Herring <robh@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: devicetree@vger.kernel.org,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Zhiqiang Hou <Zhiqiang.Hou@nxp.com>,
Marc Zyngier <maz@kernel.org>,
linux-kernel@vger.kernel.org, Shawn Guo <shawnguo@kernel.org>,
Biwen Li <biwen.li@nxp.com>,
linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Kurt Kanzenbach <kurt@linutronix.de>,
Li Yang <leoyang.li@nxp.com>
Subject: Re: [RFC PATCH devicetree 10/10] dt-bindings: ls-extirq: add a YAML schema for the validator
Date: Tue, 14 Dec 2021 09:21:25 -0600 [thread overview]
Message-ID: <1639495285.020377.3397587.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20211214013800.2703568-11-vladimir.oltean@nxp.com>
On Tue, 14 Dec 2021 03:38:00 +0200, Vladimir Oltean wrote:
> This is a conversion of the free-form description of the device tree
> bindings to a YAML schema. The description of fsl,extirq-map is best
> effort: it looks like the devicetree schema doesn't really like vendor
> properties getting too complicated, and puts a bunch of descriptions on
> what they can and can't describe. An array of uint32s is the best I
> could come up with. It doesn't help, either, that the
> schemas/interrupt-controller.yaml definition for interrupt-map, which
> I was planning to use as an inspiration, is "true # FIXME", all things
> which aren't valid in vendor properties.
>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
> ---
> .../interrupt-controller/fsl,ls-extirq.txt | 56 ---------
> .../interrupt-controller/fsl,ls-extirq.yaml | 110 ++++++++++++++++++
> 2 files changed, 110 insertions(+), 56 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.txt
> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.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:
Error: Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.example.dts:34.31-32 syntax error
FATAL ERROR: Unable to parse input tree
make[1]: *** [scripts/Makefile.lib:373: Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.example.dt.yaml] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1413: dt_binding_check] Error 2
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/patch/1567537
This check can fail if there are any dependencies. The base for a patch
series is generally the most recent rc1.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-14 15:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 1:37 [RFC PATCH devicetree 00/10] Do something about ls-extirq interrupt-map breakage Vladimir Oltean
2021-12-14 1:37 ` [RFC PATCH devicetree 01/10] irqchip/ls-extirq: rename "interrupt-map" OF property to "fsl, extirq-map" Vladimir Oltean
2021-12-14 8:46 ` [RFC PATCH devicetree 01/10] irqchip/ls-extirq: rename "interrupt-map" OF property to "fsl,extirq-map" Kurt Kanzenbach
2021-12-14 15:07 ` Rob Herring
2021-12-14 1:37 ` [RFC PATCH devicetree 02/10] Revert "arm64: dts: freescale: Fix 'interrupt-map' parent address cells" Vladimir Oltean
2021-12-14 1:37 ` [RFC PATCH devicetree 03/10] dt-bindings: ls-extirq: replace "interrupt-map" documentation with "fsl, extirq-map" Vladimir Oltean
2021-12-14 1:37 ` [RFC PATCH devicetree 04/10] arm64: dts: ls1043a: rename the "interrupt-map" of the extirq node to " Vladimir Oltean
2021-12-14 1:37 ` [RFC PATCH devicetree 05/10] arm64: dts: ls1046a: " Vladimir Oltean
2021-12-14 1:37 ` [RFC PATCH devicetree 06/10] arm64: dts: ls1088a: " Vladimir Oltean
2021-12-14 1:37 ` [RFC PATCH devicetree 07/10] arm64: dts: ls208xa: " Vladimir Oltean
2021-12-14 1:37 ` [RFC PATCH devicetree 08/10] arm64: dts: lx2160a: " Vladimir Oltean
2021-12-14 1:37 ` [RFC PATCH devicetree 09/10] ARM: dts: ls1021a: " Vladimir Oltean
2021-12-14 1:38 ` [RFC PATCH devicetree 10/10] dt-bindings: ls-extirq: add a YAML schema for the validator Vladimir Oltean
2021-12-14 15:21 ` Rob Herring [this message]
2021-12-14 8:51 ` [RFC PATCH devicetree 00/10] Do something about ls-extirq interrupt-map breakage Marc Zyngier
2021-12-14 9:58 ` Vladimir Oltean
2021-12-14 10:20 ` Marc Zyngier
2021-12-14 10:30 ` Vladimir Oltean
2021-12-14 10:39 ` Marc Zyngier
2021-12-14 10:53 ` Vladimir Oltean
2021-12-14 11:11 ` Marc Zyngier
2022-03-24 17:10 ` Vladimir Oltean
2022-03-24 17:21 ` Marc Zyngier
2022-03-24 17:34 ` Vladimir Oltean
2022-03-24 18:06 ` Marc Zyngier
2022-03-24 19:09 ` Vladimir Oltean
2022-03-24 20:14 ` Marc Zyngier
2022-03-25 10:34 ` Robin Murphy
2022-03-25 17:54 ` Vladimir Oltean
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=1639495285.020377.3397587.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Zhiqiang.Hou@nxp.com \
--cc=biwen.li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=kurt@linutronix.de \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=vladimir.oltean@nxp.com \
/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;
as well as URLs for NNTP newsgroup(s).