linux-kernel - Re: [PATCH net-next v2] dt-bindings: net: ath11k: document the inputs of the ath11k on WCN6855

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: <312fa408-d385-4b90-b8f4-729af4a3ce65@quicinc.com>
Date: Tue, 24 Sep 2024 09:46:27 -0700
From: Jeff Johnson <quic_jjohnson@...cinc.com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
        Bartosz Golaszewski
	<brgl@...ev.pl>, Kalle Valo <kvalo@...nel.org>
CC: "David S . Miller" <davem@...emloft.net>,
        Eric Dumazet
	<edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni
	<pabeni@...hat.com>, Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski
	<krzk+dt@...nel.org>,
        Conor Dooley <conor+dt@...nel.org>,
        Jeff Johnson
	<jjohnson@...nel.org>, <linux-wireless@...r.kernel.org>,
        <netdev@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <ath11k@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
        Bartosz
 Golaszewski <bartosz.golaszewski@...aro.org>,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH net-next v2] dt-bindings: net: ath11k: document the inputs
 of the ath11k on WCN6855

On 9/24/2024 1:06 AM, Krzysztof Kozlowski wrote:
> On 20/09/2024 23:02, Jeff Johnson wrote:
>> Again, since I'm a DT n00b:
>> Just to make sure I understand, you are saying that with this change any
>> existing .dts/.dtb files will still work with an updated driver, so the new
>> properties are not required to be populated on existing devices.
> 
> Did you folks rejected patches acked by DT maintainers on basis of not
> understanding DT at all?

I personally have not rejected any DT patches. Nor have I accepted any.
I'm deferring to Kalle.

>> However a new driver with support for these properties will utilize them when
>> they are present, and the current ath11k .dts files will need to be updated to
> 
> It is not related to drivers at all. Nothing in this thread is related
> to drivers.
> 
> Can we entirely drop the drivers from the discussion?

I brought up drivers since in the discussion there was concern that this DT
change would potentially break existing devices that have a DTS that defines
qcom,ath11k-calibration-variant, and I wanted clarification on that point.

/jeff