[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4c018fd1-f20e-4c16-a914-31ac7bbff800@quicinc.com>
Date: Wed, 30 Jul 2025 19:50:39 +0800
From: Luo Jie <quic_luoj@...cinc.com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
Konrad Dybcio
<konrad.dybcio@....qualcomm.com>,
Rob Herring <robh@...nel.org>,
"Krzysztof
Kozlowski" <krzysztof.kozlowski+dt@...aro.org>
CC: Georgi Djakov <djakov@...nel.org>,
Krzysztof Kozlowski
<krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Bjorn Andersson
<andersson@...nel.org>,
Michael Turquette <mturquette@...libre.com>,
"Stephen
Boyd" <sboyd@...nel.org>,
Anusha Rao <quic_anusha@...cinc.com>,
Konrad Dybcio
<konradybcio@...nel.org>,
Philipp Zabel <p.zabel@...gutronix.de>,
"Richard
Cochran" <richardcochran@...il.com>,
Catalin Marinas
<catalin.marinas@....com>,
Will Deacon <will@...nel.org>, <linux-arm-msm@...r.kernel.org>,
<linux-pm@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-clk@...r.kernel.org>,
<netdev@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
<quic_kkumarcs@...cinc.com>, <quic_linchen@...cinc.com>,
<quic_leiwei@...cinc.com>, <quic_pavir@...cinc.com>,
<quic_suruchia@...cinc.com>
Subject: Re: [PATCH v3 05/10] dt-bindings: clock: ipq9574: Rename NSS CC
source clocks to drop rate
On 7/29/2025 9:57 PM, Krzysztof Kozlowski wrote:
> On 29/07/2025 15:53, Konrad Dybcio wrote:
>>>
>>> We had adopted this proposal in version 2 previously, but as noted in
>>> the discussion linked below, Krzysztof had suggested to avoid using the
>>> clock rate in the clock names when defining the constraints for them.
>>> However I do agree that we should keep the interface for IPQ9574
>>> unchanged and instead use a generic clock name to support the newer
>>> SoCs.
>>>
>>> https://lore.kernel.org/all/20250701-optimistic-esoteric-swallow-d93fc6@krzk-bin/
>>>
>>> Request Krzysztof to provide his comments as well, on whether we can
>>> follow your suggested approach to avoid breaking ABI for IPQ9574.
>>
>> Krzysztof, should the bindings be improved-through-breaking, or should
>
>
> Unfortunately not, you should not change them for such reason.
>
>> there simply be a new YAML with un-suffixed entries, where new platforms
>> would be added down the line?
>
>
> Either new binding file or here with allOf:if:then differences per
> variant. Depends on readability.
>
OK. Thank you for the clarification.
>
> Best regards,
> Krzysztof
Powered by blists - more mailing lists