[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <EF62F8D0-A205-4D64-8540-44F843720797@goldelico.com>
Date: Sat, 28 Mar 2020 19:21:01 +0100
From: "H. Nikolaus Schaller" <hns@...delico.com>
To: Andreas Kemnade <andreas@...nade.info>
Cc: Discussions about the Letux Kernel <letux-kernel@...nphoenux.org>,
Rob Herring <robh+dt@...nel.org>,
Maxime Ripard <maxime@...no.tech>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: CHKDT error by f95cad74acdb ("dt-bindings: clocks: Convert Allwinner legacy clocks to schemas")
> Am 28.03.2020 um 18:20 schrieb Andreas Kemnade <andreas@...nade.info>:
>
> Hi Nikolaus,
>
> On Sat, 28 Mar 2020 13:26:24 +0100
> "H. Nikolaus Schaller" <hns@...delico.com> wrote:
>
>> Hi Rob,
>> I am trying to check my new bindings with v5.6-rc7 but get this before
>> the process tries mine:
>>
>> make dt_binding_check dtbs_check
>> ...
>>
>> CHKDT Documentation/devicetree/bindings/bus/renesas,bsc.yaml - due to target missing
>> CHKDT Documentation/devicetree/bindings/bus/simple-pm-bus.yaml - due to target missing
>> CHKDT Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-ahb-clk.yaml - due to target missing
>> /Volumes/CaseSensitive/master/Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-ahb-clk.yaml: Additional properties are not allowed ('deprecated' was unexpected)
>> make[2]: *** [Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-ahb-clk.example.dts] Error 1
>> make[1]: *** [dt_binding_check] Error 2
>> make: *** [sub-make] Error 2
>>
>> What am I doing wrong?
>> Is there an option to skip such errors and continue?
>> Is there an option to just test my bindings and yaml file?
>>
> maybe your tools are outdated, so rerun
>
> pip3 install git+https://github.com/devicetree-org/dt-schema.git@master
Yes, that one solves the problem!
A better error message of CHKDT would have been helpful. Or an auto-update.
Now I just get a lot of messages like
CHKDT Documentation/devicetree/bindings/arm/sunxi/allwinner,sun4i-a10-mbus.yaml - due to: Documentation/devicetree/bindings/arm/sunxi/allwinner,sun4i-a10-mbus.yaml
Documentation/devicetree/bindings/arm/sunxi/allwinner,sun4i-a10-mbus.yaml:: $id: relative path/filename doesn't match actual path or filename
expected: http://devicetree.org/schemas/arm/sunxi/allwinner,sun4i-a10-mbus.yaml:#
CHKDT Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-ahb-clk.yaml - due to target missing
Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-ahb-clk.yaml:: $id: relative path/filename doesn't match actual path or filename
expected: http://devicetree.org/schemas/clock/allwinner,sun4i-a10-ahb-clk.yaml:#
...
but they do not abort the process, except for an error found in my yaml document.
So now I can start debugging.
BR and thanks,
Nikolaus
Powered by blists - more mailing lists