netdev - Re: [PATCH v3 05/10] dt-bindings: clock: ipq9574: Rename NSS CC source clocks to drop rate

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5029ba6e-fa5f-41a5-a1df-bb9117973bd8@kernel.org>
Date: Tue, 29 Jul 2025 15:57:50 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
 Luo Jie <quic_luoj@...cinc.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 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.


Best regards,
Krzysztof