[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1j8qf92zf6.fsf@starbuckisacylon.baylibre.com>
Date: Thu, 11 Dec 2025 09:30:37 +0100
From: Jerome Brunet <jbrunet@...libre.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Jian Hu <jian.hu@...ogic.com>, Xianwei Zhao <xianwei.zhao@...ogic.com>,
Chuan Liu <chuan.liu@...ogic.com>, Neil Armstrong
<neil.armstrong@...aro.org>, Kevin Hilman <khilman@...libre.com>,
Stephen Boyd <sboyd@...nel.org>, Michael Turquette
<mturquette@...libre.com>, robh+dt <robh+dt@...nel.org>, Rob Herring
<robh@...nel.org>, devicetree <devicetree@...r.kernel.org>, linux-clk
<linux-clk@...r.kernel.org>, linux-amlogic
<linux-amlogic@...ts.infradead.org>, linux-kernel
<linux-kernel@...r.kernel.org>, linux-arm-kernel
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v6 2/5] dt-bindings: clock: add Amlogic T7 SCMI clock
controller
On Thu 11 Dec 2025 at 07:16, Krzysztof Kozlowski <krzk@...nel.org> wrote:
>>
>> Is there a new requirement to submit the DTS file changes along with the
>> driver changes now ?
>>
>> This has never been case before, especially since the changes are merged
>> through different trees.
>
> There is no such requirement, but "has never been case before" is
> clearly not accurate, because I raised this question multiple times last
> two-three years.
>
> There is no reasonable way to hold publishing of DTS, therefore if
> someone uses arguments like above with waiting for driver, I usually got
> suspicious.
>
> Also note, that many contributions from various people (not saying that
> this one here is) were bad quality and badly designed but without seeing
> DTS it takes me significantly more time to understand that design. So
> yes, publish your DTS solving all of the questions and making reviewing
> easier. Or don't and receive questions...
>
That's fair. Thanks for clarifying.
>
> Best regards,
> Krzysztof
--
Jerome
Powered by blists - more mailing lists