[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b4a23de5-3aa0-436b-b109-399b300fe876@linaro.org>
Date: Wed, 17 Jan 2024 18:29:14 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
Jerome Brunet <jbrunet@...libre.com>
Cc: Thierry Reding <thierry.reding@...il.com>,
Neil Armstrong <neil.armstrong@...aro.org>, Rob Herring
<robh+dt@...nel.org>, Krzysztof Kozlowski
<krzysztof.kozlowski+dt@...aro.org>, Conor Dooley <conor+dt@...nel.org>,
Kevin Hilman <khilman@...libre.com>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-amlogic@...ts.infradead.org,
linux-pwm@...r.kernel.org, JunYi Zhao <junyi.zhao@...ogic.com>
Subject: Re: [PATCH v4 2/6] dt-bindings: pwm: amlogic: add new compatible for
meson8 pwm type
On 17/01/2024 10:58, Uwe Kleine-König wrote:
>> - items:
>> - const: amlogic,meson-gx-pwm
>> - const: amlogic,meson-gxbb-pwm
>> + deprecated: true
>> - items:
>> - const: amlogic,meson-gx-ao-pwm
>> - const: amlogic,meson-gxbb-ao-pwm
>> + deprecated: true
>> - items:
>> - const: amlogic,meson8-pwm
>> - const: amlogic,meson8b-pwm
>> + deprecated: true
>
> I think deprecating the old binding and adding a new compatible should
> be done in two commits.
No, because you have a state with deprecated compatible and no correct
compatible. If deprecated property caused warnings, you would have
non-bisectable state.
Best regards,
Krzysztof
Powered by blists - more mailing lists