[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0a3e1b00-df93-8c81-6ecb-355bd7693ab6@huawei.com>
Date: Wed, 14 Oct 2020 09:52:42 +0800
From: "Leizhen (ThunderTown)" <thunder.leizhen@...wei.com>
To: Dan Murphy <dmurphy@...com>, Rob Herring <robh+dt@...nel.org>,
"Pavel Machek" <pavel@....cz>,
linux-leds <linux-leds@...r.kernel.org>,
Lee Jones <lee.jones@...aro.org>,
Benson Leung <bleung@...omium.org>,
"Enric Balletbo i Serra" <enric.balletbo@...labora.com>,
Guenter Roeck <groeck@...omium.org>,
Mark Brown <broonie@...nel.org>,
linux-spi <linux-spi@...r.kernel.org>,
Lubomir Rintel <lkundrak@...sk>,
devicetree <devicetree@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/6] dt-bindings: mfd: google,cros-ec: explicitly allow
additional properties
On 2020/10/14 1:53, Dan Murphy wrote:
> Zhen
>
> On 10/13/20 11:08 AM, Zhen Lei wrote:
>> There are so many properties have not been described in this yaml file,
>> and a lot of errors will be reported. Especially, some yaml files such as
>> google,cros-ec-typec.yaml, extcon-usbc-cros-ec.yaml can not pass the
>> self-check, because of the examples. So temporarily allow additional
>> properties to keep the comprehensive dt_binding_check result clean.
>
> My preference is to fix the binding to pass the checks and not just work around the issues. Working around the issues may mean the issues never get fixed.
I agree with your first sentenceļ¼don't just work around the issues. But these
errors are so annoying. Hope someone can add the description of the missing properties.
I'm not familiar with this module anyway.
And I don't fully agree with your last sentence. After all, the main properties are listed,
and the ones that are not listed should be minor ones.
>
> Dan
>
>
> .
>
Powered by blists - more mailing lists