[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZtsXUyBRV9yDeq1P@hovoldconsulting.com>
Date: Fri, 6 Sep 2024 16:53:07 +0200
From: Johan Hovold <johan@...nel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Cc: Kalle Valo <kvalo@...nel.org>, Konrad Dybcio <konradybcio@...nel.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Dmitry Baryshkov <dbaryshkov@...il.com>,
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
On Thu, Sep 05, 2024 at 10:26:04PM +0300, Dmitry Baryshkov wrote:
> On Thu, Sep 05, 2024 at 09:41:44PM GMT, Kalle Valo wrote:
> > 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?
>
> QC_8380_CRD (following DMI / Windows name) or QC_X1E80100_CRD (following
> marketing name). Or maybe QTI_ instead of QC_. WDYT?
The x1e80100 uses ath12k and the calibration data was recently pushed to
linux firmware (and does not use a calibration variant).
This thread is about sc8280xp and ath11k as I guess you've noticed by
now.
Johan
Powered by blists - more mailing lists