public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pengyu Luo <mitltlatltl@gmail.com>
To: mitltlatltl@gmail.com
Cc: andersson@kernel.org, chenxuecong2009@outlook.com,
	conor+dt@kernel.org, devicetree@vger.kernel.org,
	gty0622@gmail.com, johan+linaro@kernel.org,
	konrad.dybcio@oss.qualcomm.com, konradybcio@kernel.org,
	krzk+dt@kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: qcom: sc8280xp: Add Huawei Matebook E Go (sc8280xp)
Date: Sat, 14 Dec 2024 20:23:00 +0800	[thread overview]
Message-ID: <20241214122303.653935-1-mitltlatltl@gmail.com> (raw)
In-Reply-To: <20241213085100.564547-1-mitltlatltl@gmail.com>

On Fri, Dec 13, 2024 at 1:13 AM Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> wrote:

[...]

>> +
>> +		/* /lib/firmware/ath11k/WCN6855/hw2.1/board-2.bin
>> +		 * there is no calibrate data for huawei,
>> +		 * but they have the same subsystem-device id
>> +		 */
>> +		qcom,ath11k-calibration-variant = "LE_X13S";
> 
> Oh, this can be taken care of! See [2], [3].

[...]

Hi, Konrad

I want to distrub you again.

Finally, I found something, after I enabled ath11k boot dbg, I got my
id_string='bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=2,qmi-board-id=255`

With qca-swiss-army-knife (see [1])

$ ./ath11k-bdencoder -e board-2.bin | grep -i "$id_string"
bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=2,qmi-board-id=255.bin created size: 60048

It have already been here. So that means I don't need to extract from
Windows. I just extract it from linux-firmware then give it a variant
name and send patches to ath11k, right?

Pengyu

[1] https://github.com/qca/qca-swiss-army-knife

  parent reply	other threads:[~2024-12-14 12:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 15:37 [PATCH 0/3] arm64: dts: qcom: Introduce Huawei Matebook E Go Pengyu Luo
2024-12-11 15:37 ` [PATCH 1/3] dt-bindings: arm: qcom: Document Huawei Matebook E Go (sc8280xp) Pengyu Luo
2024-12-13 11:02   ` Krzysztof Kozlowski
2024-12-11 15:37 ` [PATCH 2/3] firmware: qcom: scm: Allow QSEECOM on " Pengyu Luo
2024-12-11 15:37 ` [PATCH 3/3] arm64: dts: qcom: sc8280xp: Add " Pengyu Luo
2024-12-12 17:13   ` Konrad Dybcio
2024-12-13  8:50     ` Pengyu Luo
2024-12-13 11:04       ` Konrad Dybcio
2024-12-13 12:21         ` Pengyu Luo
2024-12-13 12:27           ` Konrad Dybcio
2024-12-13 12:50             ` Pengyu Luo
2024-12-13 12:57               ` Konrad Dybcio
2024-12-13 13:50                 ` Pengyu Luo
2024-12-13 14:53                   ` Konrad Dybcio
2024-12-14 12:23       ` Pengyu Luo [this message]
2024-12-14 13:39         ` Dmitry Baryshkov
2024-12-14 14:48           ` Pengyu Luo
2024-12-14 16:01             ` Dmitry Baryshkov
2024-12-20 16:21           ` Johan Hovold
2024-12-21  5:26             ` Pengyu Luo
2025-01-08  8:49               ` Johan Hovold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241214122303.653935-1-mitltlatltl@gmail.com \
    --to=mitltlatltl@gmail.com \
    --cc=andersson@kernel.org \
    --cc=chenxuecong2009@outlook.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gty0622@gmail.com \
    --cc=johan+linaro@kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox