[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4a6e1a6a-78aa-62a9-1df0-4c707a1a8ec9@linaro.org>
Date: Tue, 19 Jul 2022 09:41:27 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Rob Herring <robh+dt@...nel.org>
Cc: Marek BehĂșn <kabel@...nel.org>,
Pavel Machek <pavel@....cz>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Dan Murphy <dmurphy@...com>,
Sven Schwermer <sven.schwermer@...ruptive-technologies.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Linux LED Subsystem <linux-leds@...r.kernel.org>,
devicetree@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
ChiaEn Wu <peterwu.pub@...il.com>
Subject: Re: [PATCH] dt-bindings: leds: class-multicolor: reference class
directly in multi-led node
On 18/07/2022 17:22, Rob Herring wrote:
> On Fri, Jun 24, 2022 at 5:21 AM Krzysztof Kozlowski
> <krzysztof.kozlowski@...aro.org> wrote:
>>
>> The leds/common.yaml is referenced directly in each LED node, which
>> leads to people doing the same with leds/leds-class-multicolor.yaml.
>> This is not correct because leds-class-multicolor.yaml defined multi-led
>> property and its children. Some schemas implemented this incorrect.
>>
>> Rework this to match same behavior common.yaml, so expect the multi-led
>> node to reference the leds-class-multicolor.yaml. Fixing allows to add
>> unevaluatedProperties:false.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
>>
>> ---
>>
>> This will conflict with any new users of leds-class-multicolor, e.g.:
>> https://lore.kernel.org/all/20220623115631.22209-4-peterwu.pub@gmail.com/
>>
>> The new users should be updated to match the usage introduced here.
>> ---
>> .../leds/cznic,turris-omnia-leds.yaml | 2 ++
>> .../bindings/leds/leds-class-multicolor.yaml | 32 +++++++++----------
>> .../devicetree/bindings/leds/leds-lp50xx.yaml | 2 ++
>> .../bindings/leds/leds-pwm-multicolor.yaml | 5 ++-
>> .../bindings/leds/leds-qcom-lpg.yaml | 2 ++
>> 5 files changed, 24 insertions(+), 19 deletions(-)
>
> Looks like this introduced a new warning:
>
I'll fix it.
Best regards,
Krzysztof
Powered by blists - more mailing lists