[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e10f0291-8252-fd12-5bba-f25f472cd605@linaro.org>
Date: Sun, 10 Apr 2022 17:35:55 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: "H. Nikolaus Schaller" <hns@...delico.com>
Cc: Rob Herring <robh+dt@...nel.org>,
Paul Cercueil <paul@...pouillou.net>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-mips@...r.kernel.org, letux-kernel@...nphoenux.org
Subject: Re: [PATCH 13/18] dt-bindings: fix jz4780-nemc issue as reported by
dtbscheck
On 09/04/2022 15:18, Krzysztof Kozlowski wrote:
> On 09/04/2022 15:09, H. Nikolaus Schaller wrote:
(...)
>>>> @@ -17,7 +17,7 @@ properties:
>>>> oneOf:
>>>> - enum:
>>>> -
>>>> - - ingenic,jz4780-nemc
>>>> + - [ , simple-mfd ]
>>>
>>> This is not correct representation. If you really need simple-mfd, then
>>> this should be a separate item below oneOf.
>>
>> Well, it is valid YAML syntax and seems to be accepted by dtbscheck.
Minor update:
Well, it is not a valid schema. Rob's checker now confirmed. If you run
dt_bindings_check by yourself you will see the error:
properties:compatible:oneOf:0:enum:1: ['ingenic', 'jz4780-nemc',
'simple-mfd'] is not of type 'string'
Probably because enum expects string, not another enum (so enum inside
enum is not correct).
If you do not see the error, you might be missing some packages
(mentioned in writing-schema + yamllint for a different issue) or your
dtschema is old.
>
> It's not how we code it. Please do not introduce inconsistent - even if
> valid - blocks.
Best regards,
Krzysztof
Powered by blists - more mailing lists