linux-kernel - Re: [PATCH v3 1/4] arm64: dts: qcom: sc8280xp-crd: model the PMU of the on-board 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 for Android: free password hash cracker in your pocket

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

Message-ID: <87v7zagcyf.fsf@kernel.org>
Date: Thu, 05 Sep 2024 21:41:44 +0300
From: Kalle Valo <kvalo@...nel.org>
To: Konrad Dybcio <konradybcio@...nel.org>
Cc: Bartosz Golaszewski <brgl@...ev.pl>,  Dmitry Baryshkov
 <dbaryshkov@...il.com>,  Johan Hovold <johan@...nel.org>,  Dmitry
 Baryshkov <dmitry.baryshkov@...aro.org>,  Bjorn Andersson
 <andersson@...nel.org>,  Rob Herring <robh@...nel.org>,  Krzysztof
 Kozlowski <krzk+dt@...nel.org>,  Conor Dooley <conor+dt@...nel.org>,
  linux-arm-msm@...r.kernel.org,  devicetree@...r.kernel.org,
  linux-kernel@...r.kernel.org,  Bartosz Golaszewski
 <bartosz.golaszewski@...aro.org>,
    ath11k@...ts.infradead.org
Subject: Re: [PATCH v3 1/4] arm64: dts: qcom: sc8280xp-crd: model the PMU of
 the on-board wcn6855

Konrad Dybcio <konradybcio@...nel.org> writes:

> On 5.09.2024 3:00 PM, Bartosz Golaszewski wrote:
>> On Thu, Sep 5, 2024 at 2:56 PM Dmitry Baryshkov <dbaryshkov@...il.com> wrote:
>>>
>>>>>
>>>>> As you are going to post another revision, please also add
>>>>>
>>>>> qcom,ath11k-calibration-variant
>>>>>
>>>>
>>>> I had it in earlier revisions. The only one we could add here would be
>>>> the one from X13s as QCom has not yet released the data for the CRD.
>>>> Johan and Konrad were against adding this here if it doesn't refer to
>>>> the correct one so I dropped it.
>>>
>>> As Kalle usually merges data with some delay it's not infrequent to
>>> have DTS which names calibration variant, but board-2.bin doesn't have
>>> corresponding data. The driver safely falls back to the data without
>>> variant if it can find it. Als  usually it's us who supply the
>>> calibration name.
>>>
>> 
>> Johan, Konrad,
>> 
>> What do you think? Do we know the exact name and should I add it or
>> should we wait until it's in board-2.bin?
>
> If we can agree on the string identifier with Kalle in advance, we can
> add it even before the boardfile drops

There have not been really any naming rules for the variant string, it
just needs to be unique so that it doesn't conflict with other variant
strings. What have you been thinking?

But please Cc the ath11k list for anything ath11k related, adding it
now.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches