From: Axel Rasmussen <axel.rasmussen1@gmail.com>
To: ath10k@lists.infradead.org
Subject: target IRAM recovery feature breaks QCA9984?
Date: Sat, 15 May 2021 20:51:33 -0700 [thread overview]
Message-ID: <CACC2YF2M9o4ZCY7Dj2C0xUagZkB+ymZZ9bGmzr0cKyON-KTVXA@mail.gmail.com> (raw)
Hi,
I have a QCA9984 (Compex WLE1216V5-20), which used to work on 5.10,
but starting with 5.11, and in particular this commit:
9af7c32ceca8 ath10k: add target IRAM recovery feature support
The firmware fails to load, and so the device is unusable. dmesg shows
the following:
# dmesg | grep ath
[ 12.144796] ath10k_pci 0000:04:00.0: pci irq msi oper_irq_mode 2
irq_mode 0 reset_mode 0
[ 12.272303] ath10k_pci 0000:04:00.0: qca9984/qca9994 hw1.0 target
0x01000000 chip_id 0x00000000 sub 168c:cafe
[ 12.272329] ath10k_pci 0000:04:00.0: kconfig debug 1 debugfs 1
tracing 1 dfs 1 testmode 0
[ 12.274100] ath10k_pci 0000:04:00.0: firmware ver 10.4-3.9.0.2-00131
api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 23bd9e43
[ 13.505923] ath10k_pci 0000:04:00.0: board_file api 2 bmi_id 0:31
crc32 85498734
[ 16.085259] ath10k_pci 0000:04:00.0: failed to copy target iram contents: -12
[ 16.192849] ath10k_pci 0000:04:00.0: could not init core (-12)
[ 16.193253] ath10k_pci 0000:04:00.0: could not probe fw (-12)
I'm happy to provide my kconfig or whatever else would be useful for
debugging further, or to test patches. I'd offer to write a patch, but
my knowledge of the wireless stack and ath10k in particular is rather
limited...
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
reply other threads:[~2021-05-16 3:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CACC2YF2M9o4ZCY7Dj2C0xUagZkB+ymZZ9bGmzr0cKyON-KTVXA@mail.gmail.com \
--to=axel.rasmussen1@gmail.com \
--cc=ath10k@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).