[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMRc=Mci-8R1Oe3Fe+1E+K-7khzwBPgn_8SQSUPXthpE4032Pw@mail.gmail.com>
Date: Thu, 5 Sep 2024 15:00:41 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Dmitry Baryshkov <dbaryshkov@...il.com>, Johan Hovold <johan@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>
Cc: 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>, Kalle Valo <kvalo@...nel.org>
Subject: Re: [PATCH v3 1/4] arm64: dts: qcom: sc8280xp-crd: model the PMU of
the on-board wcn6855
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?
Bart
Powered by blists - more mailing lists