Wi-Fi now works with this patch and relevant firmware
[ 21.488274] ath10k_snoc 18800000.wifi: qmi chip_id 0x30214 chip_family 0x4001 board_id 0xff soc_id 0x40030001
[ 21.498477] ath10k_snoc 18800000.wifi: qmi fw_version 0x20060285 fw_build_timestamp 2020-10-12 23:35 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HL.2.0.c4-00645-QCAHLSWMTPLZ-1.336037.2
[ 22.973165] ath10k_snoc 18800000.wifi: wcn3990 hw1.0 target 0x00000008 chip_id 0x00000000 sub 0000:0000
[ 22.983265] ath10k_snoc 18800000.wifi: kconfig debug 1 debugfs 1 tracing 0 dfs 0 testmode 0
[ 22.992048] ath10k_snoc 18800000.wifi: firmware ver api 5 features wowlan,mgmt-tx-by-reference,non-bmi crc32 b3d4b790
[ 23.045368] ath10k_snoc 18800000.wifi: htt-ver 3.83 wmi-op 4 htt-op 3 cal file max-sta 32 raw 0 hwcrypto 1
[ 23.130581] ath10k_snoc 18800000.wifi: invalid MAC address; choosing random
[ 23.139008] ath: EEPROM regdomain: 0x819a
[ 23.139018] ath: EEPROM indicates we should expect a country code
[ 23.139029] ath: doing EEPROM country->regdmn map search
[ 23.139035] ath: country maps to regdmn code: 0x5e
[ 23.139042] ath: Country alpha2 being used: KR
[ 23.139047] ath: Regpair used: 0x5e
[ 29.382642] msm_dpu ae01000.display-controller: [drm:adreno_request_fw] loaded qcom/a630_sqe.fw from new location
[ 29.395932] msm_dpu ae01000.display-controller: [drm:adreno_request_fw] loaded qcom/a630_gmu.bin from new location
[ 31.774723] Bluetooth: RFCOMM TTY layer initialized
[ 31.779713] Bluetooth: RFCOMM socket layer initialized
[ 31.784947] Bluetooth: RFCOMM ver 1.11
[ 39.138098] wlan0: authenticate with e8:9f:80:dd:68:22 (local address=ce:db:e1:ab:08:30)
[ 39.146318] wlan0: send auth to e8:9f:80:dd:68:22 (try 1/3)
[ 39.180484] wlan0: authenticate with e8:9f:80:dd:68:22 (local address=ce:db:e1:ab:08:30)
[ 39.188697] wlan0: send auth to e8:9f:80:dd:68:22 (try 1/3)
[ 39.196651] wlan0: authenticated
[ 39.202286] wlan0: associate with e8:9f:80:dd:68:22 (try 1/3)
[ 39.211036] wlan0: RX AssocResp from e8:9f:80:dd:68:22 (capab=0x111 status=0 aid=4)
[ 39.290235] wlan0: associated
[ 39.293363] wlan0: Limiting TX power to 21 (24 - 3) dBm as advertised by e8:9f:80:dd:68:22
Signed-off-by: Paul Sajna <sajattack@postmarketos.org>
---
arch/arm64/boot/dts/qcom/sdm845-lg-common.dtsi | 12 ++++++++++++
arch/arm64/boot/dts/qcom/sdm845-lg-judyln.dts | 4 ++++
2 files changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845-lg-common.dtsi b/arch/arm64/boot/dts/qcom/sdm845-lg-common.dtsi
index 0f0a3f471f48e26cc48feb1551093599fcb35d7f..2aa8f7d2f80c58b5b1f66d797879c43cd6d4533e 100644
--- a/arch/arm64/boot/dts/qcom/sdm845-lg-common.dtsi
+++ b/arch/arm64/boot/dts/qcom/sdm845-lg-common.dtsi
@@ -678,3 +678,15 @@ &uart9 {
&venus {
status = "okay";
};
+
+&wifi {
+ vdd-0.8-cx-mx-supply = <&vreg_l5a_0p8>;
+ vdd-1.8-xo-supply = <&vreg_l7a_1p8>;
+ vdd-1.3-rfa-supply = <&vreg_l17a_1p3>;
+ vdd-3.3-ch0-supply = <&vreg_l25a_3p3>;
+ vdd-3.3-ch1-supply = <&vreg_l23a_3p3>;
+
+ qcom,snoc-host-cap-skip-quirk;
+
+ status = "okay";
+};
diff --git a/arch/arm64/boot/dts/qcom/sdm845-lg-judyln.dts b/arch/arm64/boot/dts/qcom/sdm845-lg-judyln.dts
index d60094f864605f7e454693d73efb63b9a099ecad..3106fdc9b679bc6a43a1a490c61b73a63003f7e1 100644
--- a/arch/arm64/boot/dts/qcom/sdm845-lg-judyln.dts
+++ b/arch/arm64/boot/dts/qcom/sdm845-lg-judyln.dts
@@ -151,3 +151,7 @@ &bluetooth {
&venus {
firmware-name = "qcom/sdm845/lg/judyln/venus.mbn";
};
+
+&wifi {
+ qcom,calibration-variant = "lg_judyln";
+};
--
2.51.0On 9/29/25 7:05 AM, Paul Sajna wrote:
> Wi-Fi now works with this patch and relevant firmware
>
> [ 21.488274] ath10k_snoc 18800000.wifi: qmi chip_id 0x30214 chip_family 0x4001 board_id 0xff soc_id 0x40030001
> [ 21.498477] ath10k_snoc 18800000.wifi: qmi fw_version 0x20060285 fw_build_timestamp 2020-10-12 23:35 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HL.2.0.c4-00645-QCAHLSWMTPLZ-1.336037.2
> [ 22.973165] ath10k_snoc 18800000.wifi: wcn3990 hw1.0 target 0x00000008 chip_id 0x00000000 sub 0000:0000
> [ 22.983265] ath10k_snoc 18800000.wifi: kconfig debug 1 debugfs 1 tracing 0 dfs 0 testmode 0
> [ 22.992048] ath10k_snoc 18800000.wifi: firmware ver api 5 features wowlan,mgmt-tx-by-reference,non-bmi crc32 b3d4b790
> [ 23.045368] ath10k_snoc 18800000.wifi: htt-ver 3.83 wmi-op 4 htt-op 3 cal file max-sta 32 raw 0 hwcrypto 1
> [ 23.130581] ath10k_snoc 18800000.wifi: invalid MAC address; choosing random
I was only interested in this hunk ^
please trim the timestamps, too
[...]
> +&wifi {
> + vdd-0.8-cx-mx-supply = <&vreg_l5a_0p8>;
> + vdd-1.8-xo-supply = <&vreg_l7a_1p8>;
> + vdd-1.3-rfa-supply = <&vreg_l17a_1p3>;
> + vdd-3.3-ch0-supply = <&vreg_l25a_3p3>;
> + vdd-3.3-ch1-supply = <&vreg_l23a_3p3>;
> +
> + qcom,snoc-host-cap-skip-quirk;
As the dt-checker points out, there is no such property
If your wi-fi works regardless of that, you probably don't need
to set the one you intended to
Konrad
October 1, 2025 at 9:14 AM, "Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com mailto:konrad.dybcio@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E > wrote > > As the dt-checker points out, there is no such property > > If your wi-fi works regardless of that, you probably don't need > to set the one you intended to > > Konrad > Perhaps this only exists in the postmarketos tree, but it definitely exists, and doesn't work without it. I'll remove it for upstreaming for now but hopefully someone sorts that out. upstream.
On 10/2/25 6:51 AM, Paul Sajna wrote: > October 1, 2025 at 9:14 AM, "Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com mailto:konrad.dybcio@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E > wrote > > >> >> As the dt-checker points out, there is no such property >> >> If your wi-fi works regardless of that, you probably don't need >> to set the one you intended to >> >> Konrad >> > > Perhaps this only exists in the postmarketos tree, but it definitely exists, and doesn't work without it. I'll remove it for upstreaming for now but hopefully someone sorts that out. upstream. So you didn't test the tree you sent? :/ fwiw drivers/net/wireless/ath/ath10k/snoc.c: qcom,snoc-host-cap-8bit-quirk Konrad
October 2, 2025 at 9:37 AM, "Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com mailto:konrad.dybcio@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E > wrote: > > On 10/2/25 6:51 AM, Paul Sajna wrote: > > > > > October 1, 2025 at 9:14 AM, "Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com mailto:konrad.dybcio@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E > wrote > > > > > > > > > > > > As the dt-checker points out, there is no such property > > > > > > If your wi-fi works regardless of that, you probably don't need > > > to set the one you intended to > > > > > > Konrad > > > > > > > Perhaps this only exists in the postmarketos tree, but it definitely exists, and doesn't work without it. I'll remove it for upstreaming for now but hopefully someone sorts that out. upstream. > > > So you didn't test the tree you sent? :/ > > fwiw > > drivers/net/wireless/ath/ath10k/snoc.c: > qcom,snoc-host-cap-8bit-quirk > > Konrad > with qcom,snoc-host-cap-8bit-quirk I get ``` ath10k_snoc 18800000.wifi: msa info req rejected: 90 ``` without it I get ``` ath10k_snoc 18800000.wifi: host capability request rejected: 1 ``` Please help me understand how I should proceed.
November 25, 2025 at 6:40 AM, "Paul Sajna" <sajattack@postmarketos.org mailto:sajattack@postmarketos.org?to=%22Paul%20Sajna%22%20%3Csajattack%40postmarketos.org%3E > wrote: > > October 2, 2025 at 9:37 AM, "Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com mailto:konrad.dybcio@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E > wrote: > > > > > On 10/2/25 6:51 AM, Paul Sajna wrote: > > > > > > October 1, 2025 at 9:14 AM, "Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com mailto:konrad.dybcio@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E > wrote > > > > > > > > > > > > As the dt-checker points out, there is no such property > > > > > > If your wi-fi works regardless of that, you probably don't need > > > to set the one you intended to > > > > > > Konrad > > > > > > > Perhaps this only exists in the postmarketos tree, but it definitely exists, and doesn't work without it. I'll remove it for upstreaming for now but hopefully someone sorts that out. upstream. > > > > So you didn't test the tree you sent? :/ > > > > fwiw > > > > drivers/net/wireless/ath/ath10k/snoc.c: > > qcom,snoc-host-cap-8bit-quirk > > > > Konrad > > > with qcom,snoc-host-cap-8bit-quirk I get > ``` > ath10k_snoc 18800000.wifi: msa info req rejected: 90 > ``` > > without it I get > ``` > ath10k_snoc 18800000.wifi: host capability request rejected: 1 > > ``` > > Please help me understand how I should proceed. > I guess I'll just voice my support in https://patchwork.kernel.org/project/ath10k/patch/1601058581-19461-1-git-send-email-amit.pundir@linaro.org/ for now.
On Tue, Nov 25, 2025 at 06:51:00AM +0000, Paul Sajna wrote: > November 25, 2025 at 6:40 AM, "Paul Sajna" <sajattack@postmarketos.org mailto:sajattack@postmarketos.org?to=%22Paul%20Sajna%22%20%3Csajattack%40postmarketos.org%3E > wrote: > > > > > > October 2, 2025 at 9:37 AM, "Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com mailto:konrad.dybcio@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E > wrote: > > > > > > > > On 10/2/25 6:51 AM, Paul Sajna wrote: > > > > > > > > > October 1, 2025 at 9:14 AM, "Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com mailto:konrad.dybcio@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E > wrote > > > > > > > > > > > > > > > > > As the dt-checker points out, there is no such property > > > > > > > > If your wi-fi works regardless of that, you probably don't need > > > > to set the one you intended to > > > > > > > > Konrad > > > > > > > > > > Perhaps this only exists in the postmarketos tree, but it definitely exists, and doesn't work without it. I'll remove it for upstreaming for now but hopefully someone sorts that out. upstream. > > > > > > So you didn't test the tree you sent? :/ > > > > > > fwiw > > > > > > drivers/net/wireless/ath/ath10k/snoc.c: > > > qcom,snoc-host-cap-8bit-quirk > > > > > > Konrad > > > > > with qcom,snoc-host-cap-8bit-quirk I get > > ``` > > ath10k_snoc 18800000.wifi: msa info req rejected: 90 > > ``` > > > > without it I get > > ``` > > ath10k_snoc 18800000.wifi: host capability request rejected: 1 > > > > ``` > > > > Please help me understand how I should proceed. > > > > I guess I'll just voice my support in https://patchwork.kernel.org/project/ath10k/patch/1601058581-19461-1-git-send-email-amit.pundir@linaro.org/ for now. Can "... we just ignore the return value of ath10k_qmi_host_cap_send_sync() and move along"? -- With best wishes Dmitry
On 26/11/2025 01:38, Dmitry Baryshkov wrote: [...] >>> with qcom,snoc-host-cap-8bit-quirk I get >>> ``` >>> ath10k_snoc 18800000.wifi: msa info req rejected: 90 >>> ``` >>> >>> without it I get >>> ``` >>> ath10k_snoc 18800000.wifi: host capability request rejected: 1 >>> >>> ``` >>> >>> Please help me understand how I should proceed. >>> >> >> I guess I'll just voice my support in https://patchwork.kernel.org/project/ath10k/patch/1601058581-19461-1-git-send-email-amit.pundir@linaro.org/ for now. > > Can "... we just ignore the return value of > ath10k_qmi_host_cap_send_sync() and move along"? > From: https://lore.kernel.org/all/20201029134017.GA807@yoga/ SNIP --- > Why can't you just always ignore this error? If you can't deal with this > entirely in the driver, then it should be part of the WiFi firmware so > it's always in sync. > Unfortunately the firmware versions I've hit this problem on has gone belly up when receiving this request, that's why I asked Amit to add a flag to skip it. That said, in the devices I've hit this I've managed to get newer firmware working, which doesn't have either problem. SNIP --- That's the pain behind it. David
October 2, 2025 at 9:37 AM, "Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com mailto:konrad.dybcio@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E > wrote: > > On 10/2/25 6:51 AM, Paul Sajna wrote: > > > > > October 1, 2025 at 9:14 AM, "Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com mailto:konrad.dybcio@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E > wrote > > > > > > > > > > > > As the dt-checker points out, there is no such property > > > > > > If your wi-fi works regardless of that, you probably don't need > > > to set the one you intended to > > > > > > Konrad > > > > > > > Perhaps this only exists in the postmarketos tree, but it definitely exists, and doesn't work without it. I'll remove it for upstreaming for now but hopefully someone sorts that out. upstream. > > > So you didn't test the tree you sent? :/ > > fwiw > > drivers/net/wireless/ath/ath10k/snoc.c: > qcom,snoc-host-cap-8bit-quirk > > Konrad > I think I'll probably just drop this until a bunch of other stuff is upstreamed. mdss is totally broken on mainline, wi-fi doesn't work, fuel gauge is missing, etc. etc. I tried the 8-bit quirk and it didn't help.
On Thu, Oct 02, 2025 at 07:26:16PM +0000, Paul Sajna wrote: > October 2, 2025 at 9:37 AM, "Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com mailto:konrad.dybcio@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E > wrote: > > > > > > On 10/2/25 6:51 AM, Paul Sajna wrote: > > > > > > > > October 1, 2025 at 9:14 AM, "Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com mailto:konrad.dybcio@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E > wrote > > > > > > > > > > > > > > > > > As the dt-checker points out, there is no such property > > > > > > > > If your wi-fi works regardless of that, you probably don't need > > > > to set the one you intended to > > > > > > > > Konrad > > > > > > > > > > Perhaps this only exists in the postmarketos tree, but it definitely exists, and doesn't work without it. I'll remove it for upstreaming for now but hopefully someone sorts that out. upstream. > > > > > So you didn't test the tree you sent? :/ > > > > fwiw > > > > drivers/net/wireless/ath/ath10k/snoc.c: > > qcom,snoc-host-cap-8bit-quirk > > > > Konrad > > > > I think I'll probably just drop this until a bunch of other stuff is upstreamed. mdss is totally broken on mainline, wi-fi doesn't work, fuel gauge is missing, etc. etc. Please make sure that the parts you are sending upstream are actually working on the upstream tree. Otherwise somebody might try running upstream without extra patches and be surprised about it not working. The patchseres in question was submitted in 2020 and got rejected. Since that time we have added support for machine-specific firmware-N.bin, so Kalle's suggestion can now be implemented easily. Regarding the MDSS. Is it being solved by adding reset to the MDSS node? Or are there any other issues? > > I tried the 8-bit quirk and it didn't help. -- With best wishes Dmitry
October 3, 2025 at 5:13 PM, "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com mailto:dmitry.baryshkov@oss.qualcomm.com?to=%22Dmitry%20Baryshkov%22%20%3Cdmitry.baryshkov%40oss.qualcomm.com%3E > wrote: > Regarding the MDSS. Is it being solved by adding reset to the MDSS node? > Or are there any other issues? Yes I'm referring to the reset / pmdomain issue. Joel Selvaraj is looking into it in the sdm845 tree. He said he tried doing what other SOCs did and it just got stuck in a reboot loop. More investigation required. Currently he's reverted the pmdomain commits in our tree.
On Fri, Oct 03, 2025 at 06:52:03PM +0000, Paul Sajna wrote: > October 3, 2025 at 5:13 PM, "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com mailto:dmitry.baryshkov@oss.qualcomm.com?to=%22Dmitry%20Baryshkov%22%20%3Cdmitry.baryshkov%40oss.qualcomm.com%3E > wrote: > > > > > Regarding the MDSS. Is it being solved by adding reset to the MDSS node? > > Or are there any other issues? > > Yes I'm referring to the reset / pmdomain issue. Joel Selvaraj is looking into it in the sdm845 tree. He said he tried doing what other SOCs did and it just got stuck in a reboot loop. More investigation required. Currently he's reverted the pmdomain commits in our tree. Which pmdomain commits? -- With best wishes Dmitry
October 3, 2025 at 7:36 PM, "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com mailto:dmitry.baryshkov@oss.qualcomm.com?to=%22Dmitry%20Baryshkov%22%20%3Cdmitry.baryshkov%40oss.qualcomm.com%3E > wrote: > > On Fri, Oct 03, 2025 at 06:52:03PM +0000, Paul Sajna wrote: > > > > > October 3, 2025 at 5:13 PM, "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com mailto:dmitry.baryshkov@oss.qualcomm.com?to=%22Dmitry%20Baryshkov%22%20%3Cdmitry.baryshkov%40oss.qualcomm.com%3E > wrote: > > > > > > > > Regarding the MDSS. Is it being solved by adding reset to the MDSS node? > > Or are there any other issues? > > > > Yes I'm referring to the reset / pmdomain issue. Joel Selvaraj is looking into it in the sdm845 tree. He said he tried doing what other SOCs did and it just got stuck in a reboot loop. More investigation required. Currently he's reverted the pmdomain commits in our tree. > > > Which pmdomain commits? > > -- > With best wishes > Dmitry > https://gitlab.com/sdm845-mainline/linux/-/commit/002ebddd695a53999550e241b71950f1aa0e1ac4 https://gitlab.com/sdm845-mainline/linux/-/commit/09813cde376d9d8f30eaf761534532101a0a7755 https://gitlab.com/sdm845-mainline/linux/-/commit/0e789b491ba04c31de5c71249487593e386baa67 https://gitlab.com/sdm845-mainline/linux/-/commit/13a4b7fb62600e1c0738fdb0b7176555ff05aadf All got reverted in the sdm845-mainline tree, I believe related to fixing mdss https://gitlab.com/sdm845-mainline/linux/-/commits/sdm845%2F6.17-wip
On Fri, Oct 03, 2025 at 07:55:21PM +0000, Paul Sajna wrote: > October 3, 2025 at 7:36 PM, "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com mailto:dmitry.baryshkov@oss.qualcomm.com?to=%22Dmitry%20Baryshkov%22%20%3Cdmitry.baryshkov%40oss.qualcomm.com%3E > wrote: > > > > > > On Fri, Oct 03, 2025 at 06:52:03PM +0000, Paul Sajna wrote: > > > > > > > > October 3, 2025 at 5:13 PM, "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com mailto:dmitry.baryshkov@oss.qualcomm.com?to=%22Dmitry%20Baryshkov%22%20%3Cdmitry.baryshkov%40oss.qualcomm.com%3E > wrote: > > > > > > > > > > > > Regarding the MDSS. Is it being solved by adding reset to the MDSS node? > > > Or are there any other issues? > > > > > > Yes I'm referring to the reset / pmdomain issue. Joel Selvaraj is looking into it in the sdm845 tree. He said he tried doing what other SOCs did and it just got stuck in a reboot loop. More investigation required. Currently he's reverted the pmdomain commits in our tree. > > > > > Which pmdomain commits? > > > > -- > > With best wishes > > Dmitry > > > > https://gitlab.com/sdm845-mainline/linux/-/commit/002ebddd695a53999550e241b71950f1aa0e1ac4 > https://gitlab.com/sdm845-mainline/linux/-/commit/09813cde376d9d8f30eaf761534532101a0a7755 > https://gitlab.com/sdm845-mainline/linux/-/commit/0e789b491ba04c31de5c71249487593e386baa67 > https://gitlab.com/sdm845-mainline/linux/-/commit/13a4b7fb62600e1c0738fdb0b7176555ff05aadf Thanks for the pointers. > > All got reverted in the sdm845-mainline tree, I believe related to fixing mdss > https://gitlab.com/sdm845-mainline/linux/-/commits/sdm845%2F6.17-wip -- With best wishes Dmitry
© 2016 - 2026 Red Hat, Inc.