[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <18bdf4ae-c445-ad10-b344-324436cbe445@canonical.com>
Date: Wed, 23 Feb 2022 08:09:39 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
Heiko Stuebner <heiko@...ech.de>
Cc: linux-mediatek@...ts.infradead.org,
Douglas Anderson <dianders@...omium.org>,
Lee Jones <lee.jones@...aro.org>, linux-pwm@...r.kernel.org,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Benson Leung <bleung@...omium.org>,
linux-arm-msm@...r.kernel.org, chrome-platform@...ts.linux.dev,
devicetree@...r.kernel.org,
Thierry Reding <thierry.reding@...il.com>,
linux-rockchip@...ts.infradead.org, Andy Gross <agross@...nel.org>,
linux-arm-kernel@...ts.infradead.org,
Matthias Brugger <matthias.bgg@...il.com>,
Guenter Roeck <groeck@...omium.org>,
linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH 0/4] mfd/pwm: dt-bindings: google, cros-ec:
include generic pwm schema
On 23/02/2022 07:22, Uwe Kleine-König wrote:
> Hello,
>
> On Wed, Feb 23, 2022 at 12:27:08AM +0100, Heiko Stuebner wrote:
>> On Mon, 14 Feb 2022 09:19:12 +0100, Krzysztof Kozlowski wrote:
>>> DTS patches are independent. Not tested, but I really hope no downstream kernel
>>> depends on pwm node naming... If it does, please change it to compatible. :)
>>>
>>> Best regards,
>>> Krzysztof
>>>
>>> Krzysztof Kozlowski (4):
>>> dt-bindings: pwm: google,cros-ec: include generic pwm schema
>>> arm64: dts: mt8183: align Google CROS EC PWM node name with dtschema
>>> arm64: dts: qcom: align Google CROS EC PWM node name with dtschema
>>> arm64: dts: rk3399: align Google CROS EC PWM node name with dtschema
>>>
>>> [...]
>>
>> Applied, thanks!
>>
>> [4/4] arm64: dts: rk3399: align Google CROS EC PWM node name with dtschema
>> commit: 474a84be692d893f45a54b405dcbc137cbf77949
>
> I expected that all patches in this series go in together via an ARM
> tree. Or are there expectations that this goes via PWM?
I would propose to pick individual patches by each maintainer. bindings
by PWM tree (Rob acked it) and DTS via each SoC tree.
Such approach gives flexibility, although `make dtbs_check` will spot
the new errors when run in PWM tree. Next will be fine, though.
Best regards,
Krzysztof
Powered by blists - more mailing lists