From: Jerome Brunet <jbrunet@baylibre.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
Thierry Reding <thierry.reding@gmail.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-amlogic@lists.infradead.org, linux-pwm@vger.kernel.org,
JunYi Zhao <junyi.zhao@amlogic.com>
Subject: Re: [PATCH v2 5/6] arm: dts: amlogic: migrate pwms to new meson8 v2 binding
Date: Wed, 22 Nov 2023 15:52:56 +0100 [thread overview]
Message-ID: <1jsf4xeskb.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <f04d8ad1-4411-4334-8d22-0aa757bf227c@linaro.org>
On Wed 22 Nov 2023 at 09:39, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> On 17/11/2023 13:59, Jerome Brunet wrote:
>> Update Amlogic based SoC PWMs to meson8-pwm-v2 compatible
>
> Why? Your commit msg must explain this. You break users of this DTS on
> older kernels and also this makes it impossible to apply via different
> branches in the same cycle. All this needs explanation and proper
> justification. Your message tells here nothing, because "what" is quite
> obvious.
>
I provided all the explanation possible through the different commits of
this series. I can re-state here if it helps
>>
>> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
>> ---
>> arch/arm/boot/dts/amlogic/meson.dtsi | 4 ++--
>> arch/arm/boot/dts/amlogic/meson8.dtsi | 16 +++++++++++++---
>> arch/arm/boot/dts/amlogic/meson8b-ec100.dts | 2 --
>> arch/arm/boot/dts/amlogic/meson8b-mxq.dts | 2 --
>> arch/arm/boot/dts/amlogic/meson8b-odroidc1.dts | 2 --
>> arch/arm/boot/dts/amlogic/meson8b.dtsi | 16 +++++++++++++---
>> 6 files changed, 28 insertions(+), 14 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/amlogic/meson.dtsi b/arch/arm/boot/dts/amlogic/meson.dtsi
>> index 8e3860d5d916..80cc004ad5fe 100644
>> --- a/arch/arm/boot/dts/amlogic/meson.dtsi
>> +++ b/arch/arm/boot/dts/amlogic/meson.dtsi
>> @@ -83,14 +83,14 @@ i2c_A: i2c@8500 {
>> };
>>
>> pwm_ab: pwm@8550 {
>> - compatible = "amlogic,meson-pwm";
>> + compatible = "amlogic,meson8-pwm-v2";
>
> That's breaking users of this DTS (old kernel, out of tree, other
> projects) for no real reasons without explanation.
"amlogic,meson-pwm" will continue to match, meaning of bindings is unchanged
How do you propose to fix badly designed bindings then ?
if we cant even introduce a new compatible to fix things up. It is supposed to
stay and broken till the end of time ?
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2023-11-22 15:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 12:59 [PATCH v2 0/6] pwm: meson: dt-bindings fixup Jerome Brunet
2023-11-17 12:59 ` [PATCH v2 1/6] dt-bindings: pwm: amlogic: fix s4 bindings Jerome Brunet
2023-11-19 16:04 ` Rob Herring
2023-11-17 12:59 ` [PATCH v2 2/6] dt-bindings: pwm: amlogic: add new compatible for meson8 pwm type Jerome Brunet
2023-11-19 16:05 ` Rob Herring
2023-11-20 8:27 ` Neil Armstrong
2023-11-20 9:18 ` Jerome Brunet
2023-11-20 9:55 ` neil.armstrong
2023-11-20 10:04 ` Jerome Brunet
2023-11-22 8:37 ` Krzysztof Kozlowski
2023-11-22 14:34 ` Jerome Brunet
2023-11-22 15:04 ` Krzysztof Kozlowski
2023-11-22 15:23 ` Jerome Brunet
2023-11-22 15:46 ` Krzysztof Kozlowski
2023-11-22 16:14 ` Jerome Brunet
2023-11-22 18:09 ` Krzysztof Kozlowski
2023-11-17 12:59 ` [PATCH v2 3/6] pwm: meson: prepare addition of new compatible types Jerome Brunet
2023-11-17 12:59 ` [PATCH v2 4/6] pwm: meson: add generic compatible for meson8 to sm1 Jerome Brunet
2023-11-17 12:59 ` [PATCH v2 5/6] arm: dts: amlogic: migrate pwms to new meson8 v2 binding Jerome Brunet
2023-11-22 8:39 ` Krzysztof Kozlowski
2023-11-22 14:52 ` Jerome Brunet [this message]
2023-11-22 15:10 ` Krzysztof Kozlowski
2023-11-17 12:59 ` [PATCH v2 6/6] arm64: " Jerome Brunet
2023-11-22 8:41 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1jsf4xeskb.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=junyi.zhao@amlogic.com \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox