Re: [PATCH 2/3] arm64: dts: qcom: glymur: Add Asus Zenbook A14 (UX3407NA)
Nicko van Someren <[email protected]> Mon, 3 Aug 2026 10:19:33 -0600
| Newsgroups | org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On Jun 22, 2026, at 19:31, Bjorn Andersson <[email protected]> wrote: > From: Bjorn Andersson <[email protected]> >=20 > UX3407NA is a variant of the Asus Zenbook A14 built on the Qualcomm > Glymur platform. It comes with an 18-core X2 Elite SoC, 32GB DDR, and > the other typical Glymur platform capabilities. Firstly, many thanks for this. I recently acquired one of these machines for some firmware work I'm doing and having a working Linux system on it makes my life much easier! I tested this patch set, along with the others it depends on. I have it mostly working now but ran into some issues that might indicate a few changes. WIFI: > + wifi@0 { > + compatible =3D "pci17cb,1107"; > ... > + }; ASUS don't specify what WiFi7 chip they use, which is fairly normal = since ASUS tends to swap the parts depending on supply. As a result, my = machine has a QCC2072 (17cb:1112) WiFi/BT module not the WCN7850 (17cb:1107) = device that you listed. Inspection of the hardware shows that the WiFi/BT = module is a solder-down M.2 LGA module, but electrically that's still an M.2 interface. Photos that I can find of the Zenbook A16 show it does the = same. I think it might be more reliable to define a wlan-connector, like = Konrad Dybcio did in the Asus Zenbook A16 (UX3607OA) (2/3) from 2026-07-21, rather than specify the chip. SOUND: Regarding sound definitions, the dts declares four WSA8845s -- a woofer and tweeter per side, two on swr0 and two on swr3.=20 > +&swr0 { > + status =3D "okay"; > + > + /* WSA8845, left woofer */ > ... > + > + /* WSA8845, left tweeter */ > ... > +}; > + > +&swr3 { > + status =3D "okay"; > ... > + /* WSA8845, right woofer */ > ... > + > + /* WSA8845, right tweeter */ > ... > +}; This machine only has two speakers (again confirmed by physical = inspection). Only swr0 shows attached on /sys/bus/soundwire/devices/sdw:*/status: sdw:1:0:0217:0204:00:0 Attached sdw:1:0:0217:0204:00:1 Attached sdw:4:0:0217:0204:00:0 UNATTACHED sdw:4:0:0217:0204:00:1 UNATTACHED I don't think that's a config fault either; the swr0 and swr3 reset = lines are both claimed and in identical state of (out, 0, 2mA, no pull). It's not = really a surprise that the cheaper model from ASUS would not use the full spec = audio offered on the Qualcomm reference designs, but without a suitable UX3407NA-tplg.bin topology file I can't really tell more. It appears that the audio setup is blocked further up the audio stack = anyway. I hacked some dts changes, purloined blobs from Windows and got a stereo = speaker setup configured. SoundWire is healthy, but no audio is possible because = the DSP does not respond. The ADSP boots and the audio PD is reported up: remoteproc remoteproc1: remote processor adsp is now up PDR: Indication received from msm/adsp/audio_pd, state: 0x1fffffff qcom,apr ...: Adding APR/GPR dev: gprsvc:service:2:1 then, on every boot: qcom-apm gprsvc:service:2:1: CMD timeout for [1001021] opcode I'm curious as to if you tested this (or if this even known to work on = the Zenbook A16, Yoga Slim 7x or EliteBook X G2q with the other = submissions). Do you know if/when the required firmware blobs will be forthcoming and upstreamed? HDMI: The built-in HDMI cannot read EDID: the connector reports "connected" = with a monitor attached but the EDID is 0 bytes and there are no modes. Less = than 2 seconds into every boot, before any cable is involved: gcc_usb3_tert_phy_com_aux_clk status stuck at 'off' Failed to enable clk 'com_aux': -16 phy phy-88e1000.phy.5: phy init failed --> -16 I have not really investigated this in detail. eDP: eDP link training intermittently times out on resume, leaving visible = flicker until another suspend/resume retrains it: [drm:msm_dp_ctrl_link_train_1_2] *ERROR* link training #2 on phy 0 = failed. ret=3D-110 I am carrying the (unmerged) "phy: qcom: edp: update v8 power-on programming sequence" series, so this may be feedback for that rather = than a report against mainline. Anyway, thank you again for this patch series. It got me to the point of having a very usable machine for my limited needs. If you have updates = the need testing I'm happy to help. Nicko