From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Aleksandrs Vinarskis <alex@vinarskis.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Subject: Re: [PATCH v2 3/3] arm64: dts: qcom: x1e80100-asus-zenbook-a14: Enable WiFi, Bluetooth
Date: Sat, 27 Sep 2025 14:23:08 +0200 [thread overview]
Message-ID: <764bc5f3-4387-4462-87cc-d8787b1be0ce@oss.qualcomm.com> (raw)
In-Reply-To: <20250926-zenbook-improvements-v2-3-c0b512ab6b57@vinarskis.com>
On 9/26/25 9:08 AM, Aleksandrs Vinarskis wrote:
> Unlike UX3407QA with ath11k, UX3407RA comes with ath12k. Definitions
> were not added during initial bringup due to lack of hardware to test
ath1xk is the name of the driver, WCNxyzabc123 is the preferred way
to refer to the hw, as that's the actual chip identifier
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
prev parent reply other threads:[~2025-09-27 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 7:08 [PATCH v2 0/3] arm64: dts: qcom: x1-asus-zenbook-a14: LCD, WiFi for X1E support Aleksandrs Vinarskis
2025-09-26 7:08 ` [PATCH v2 1/3] dt-bindings: arm: qcom: Add Asus Zenbook A14 UX3407QA LCD/OLED variants Aleksandrs Vinarskis
2025-09-26 7:08 ` [PATCH v2 2/3] arm64: dts: qcom: Rework X1-based Asus Zenbook A14's displays Aleksandrs Vinarskis
2025-09-26 22:32 ` Dmitry Baryshkov
2025-09-27 11:59 ` Aleksandrs Vinarskis
2025-09-27 12:21 ` Konrad Dybcio
2025-09-26 7:08 ` [PATCH v2 3/3] arm64: dts: qcom: x1e80100-asus-zenbook-a14: Enable WiFi, Bluetooth Aleksandrs Vinarskis
2025-09-27 12:23 ` Konrad Dybcio [this message]
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=764bc5f3-4387-4462-87cc-d8787b1be0ce@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=alex@vinarskis.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--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
all inboxes | Powered by JetHome®