[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <783a67ad-ee7e-c75a-a52c-672cd355bd37@canonical.com>
Date: Wed, 12 Jan 2022 08:42:52 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Pavel Machek <pavel@....cz>, Rob Herring <robh+dt@...nel.org>,
Lee Jones <lee.jones@...aro.org>,
Javier Martinez Canillas <javier@...hile0.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
linux-leds@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 3/3] dt-bindings: leds: common: fix unit address in
max77693 example
On 11/01/2022 18:54, Krzysztof Kozlowski wrote:
> The max77693 LED device node should not take an unit address, because it
> is instantiated from a max77693 I2C parent device node. This also
> splits all examples to separate DTS examples because they are actually
> independent.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
> ---
> Documentation/devicetree/bindings/leds/common.yaml | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
This should be part of my max77693 patchset:
https://lore.kernel.org/lkml/20220111175017.223966-1-krzysztof.kozlowski@canonical.com/
Nothing actually depends on this patch. It just fixes a warning which
will be brought to eyes with mentioned max77693 patchset.
Pavel, feel free to take it separately via leds tree. Other way is to
take it with other max77693 patches (probably via MFD tree).
Best regards,
Krzysztof
Powered by blists - more mailing lists