search

sdm660-mainline / linux

Linux-sdm660 kernel source tree
Other
27 stars 17 forks source link

fixup! arm64: dts: qcom: add device-tree for Redmi Note 6 Pro (tulip) #22

Closed M0Rf30 closed 7 months ago

M0Rf30 commented 7 months ago

After some analysis, removed regions are the same as declared within in sdm660.dtsi. This sports:

Known issues:

[   65.457083] qcom-q6v5-mss 4080000.remoteproc: fatal error received: err_qdi.c:459:EX:wlan_process:1:WLAN RT:1087:PC=b00c87e0
[   65.465433] remoteproc remoteproc1: crash detected in 4080000.remoteproc: type fatal error
[   65.473827] remoteproc remoteproc1: handling crash #3 in 4080000.remoteproc
[   65.482046] remoteproc remoteproc1: recovering 4080000.remoteproc
[   65.524203] ath10k_snoc 18800000.wifi: firmware crashed! (guid ad8cb34b-385c-4465-8e32-c02cb94593f6)
[   65.532747] ath10k_snoc 18800000.wifi: wcn3990 hw1.0 target 0x00000008 chip_id 0x00000000 sub 0000:0000
[   65.540995] ath10k_snoc 18800000.wifi: kconfig debug 1 debugfs 1 tracing 0 dfs 0 testmode 0
[   65.549050] ath10k_snoc 18800000.wifi: firmware ver 1.0.0.591 api 5 features wowlan,mgmt-tx-by-reference,non-bmi crc32 b3d4b790
[   65.557163] ath10k_snoc 18800000.wifi: board_file api 2 bmi_id N/A crc32 00000000
[   65.565221] ath10k_snoc 18800000.wifi: htt-ver 3.58 wmi-op 4 htt-op 3 cal file max-sta 32 raw 0 hwcrypto 1
[   65.594267] qcom-q6v5-mss 4080000.remoteproc: port failed halt
[   65.608939] remoteproc remoteproc1: stopped remote processor 4080000.remoteproc
[   65.730295] qcom-q6v5-mss 4080000.remoteproc: MBA booted without debug policy, loading mpss
[   67.384927] remoteproc remoteproc1: remote processor 4080000.remoteproc is now up
[   68.574331] ath10k_snoc 18800000.wifi: failed to set PS Mode 1 for vdev 0: -108
[   68.594242] ath10k_snoc 18800000.wifi: failed to setup powersave: -108
[   68.610239] ath10k_snoc 18800000.wifi: failed to setup ps on vdev 0: -108
[   68.626277] ath10k_snoc 18800000.wifi: failed to set vdev wmm params on vdev 1: -108
[   68.642312] ath10k_snoc 18800000.wifi: failed to set vdev wmm params on vdev 1: -108
[   68.658252] ath10k_snoc 18800000.wifi: failed to set vdev wmm params on vdev 1: -108
[   68.674252] ath10k_snoc 18800000.wifi: failed to set vdev wmm params on vdev 1: -108
[   68.690251] ath10k_snoc 18800000.wifi: device successfully recovered
[   70.015739] ath10k_snoc 18800000.wifi: failed to start hw scan: -108
[   70.436591] ieee80211 phy0: Hardware restart was requested

I've already done lots of attempts with qca-swissarmyknife and official ath10k board-2.bin and firmware-5.bin but firmware crashes after a while.

Wifi APs are detected and associated.

minlexx commented 7 months ago

Can you post full dmesg log since time stamp 0? Or at least since the first moment ath10k probes. I'm interested in messages like

[ 23.219133] ath10k_snoc 18800000.wifi: qmi chip_id 0x140 chip_family 0x4002 board_id 0xff soc_id 0x40050000
[ 23.226119] ath10k_snoc 18800000.wifi: qmi fw_version 0x10128219 fw_build_timestamp 2018-11-05 21:43 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HL.1.0.1.c2-00537-QCAHLSWMTPLZ-1
M0Rf30 commented 7 months ago

Can you post full dmesg log since time stamp 0? Or at least since the first moment ath10k probes. I'm interested in messages like

[ 23.219133] ath10k_snoc 18800000.wifi: qmi chip_id 0x140 chip_family 0x4002 board_id 0xff soc_id 0x40050000
[ 23.226119] ath10k_snoc 18800000.wifi: qmi fw_version 0x10128219 fw_build_timestamp 2018-11-05 21:43 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HL.1.0.1.c2-00537-QCAHLSWMTPLZ-1
[   31.507183] ath10k_snoc 18800000.wifi: qmi chip_id 0x140 chip_family 0x4002 board_id 0xff soc_id 0x40050000
[   31.507412] zram0: detected capacity change from 0 to 3776512
[   31.514917] ath10k_snoc 18800000.wifi: qmi fw_version 0x101c821a fw_build_timestamp 2019-07-25 03:17 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HL.1.0.1.c2-00538-QCAHLSWMTPLZ-1.214870.1
minlexx commented 7 months ago
  1. Is diag-router service running?
  2. Have you tried in json that's used as input to ath10k-bdencoder, leave only entry with board_id 0xff ?

In other words, use only

[
  {
          "data": "bdf/bdwlan.bin",
          "names": ["bus=snoc,qmi-board-id=ff"]
  }
]

as input to ath10k-bdencoder, without all other entries. Will it crash less?

M0Rf30 commented 7 months ago
  1. Is diag-router service running?
  2. Have you tried in json that's used as input to ath10k-bdencoder, leave only entry with board_id 0xff ?

In other words, use only

[
  {
          "data": "bdf/bdwlan.bin",
          "names": ["bus=snoc,qmi-board-id=ff"]
  }
]

as input to ath10k-bdencoder, without all other entries. Will it crash less?

already tried, also with chip-id=140. but nothing meaningful what I should expect from diag-router? I only see something related to modem

minlexx commented 7 months ago

what I should expect from diag-router?

Nothing specific, it should be running and you should see DIAG services in qrtr-lookup output.

Well, I have no other suggestions and I'm not expert in tulip's reserved memory, I'm assuming you know better.