From: "Hermida, Isaac" <Isaac.Hermida@digi.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: ath10k-sdio: failed to load firmware
Date: Mon, 1 Jul 2019 12:02:06 +0000 [thread overview]
Message-ID: <5D19F63D.8000302@digi.com> (raw)
Hi guys,
I know that it is still under development, but I am trying to use the ath10k driver with SDIO support on the QCA6574 chip. At least, based on all the commits, I should be able to load the firmware and have at least a minimal support (station), but currently I am unable to load the FW correctly.
I am using the latest "firmware-sdio-6.bin_WLAN.RMH.4.4.1-00011-QCARMSWP-2", board.bin and board-2.bin from [1].
"""
# md5sum *
db8264c352f202f38dfb99175209274c board-2.bin
cb37c63d9ca28f53fea1ff09ad7c7a82 board.bin
2e18e9b185e2f5f0940ca26f9f608f4a firmware-sdio-6.bin
"""
I am using an upstream kernel "5.1.14" and commit " a7891b029909009ffa4cd7b62593979f3d91aef7" from [2].
The load of the driver fails as:
"""
# dmesg | grep -iE "ath10k|mmc"
<4>ath10k_sdio mmc0:0001:1: WARNING: ath10k SDIO support is work-in-progress, problems may arise!
<6>ath10k_sdio mmc0:0001:1: qca6174 hw3.2 sdio target 0x05030000 chip_id 0x00000000 sub 0000:0000
<6>ath10k_sdio mmc0:0001:1: kconfig debug 1 debugfs 0 tracing 0 dfs 0 testmode 0
<6>ath10k_sdio mmc0:0001:1: firmware ver WLAN.RMH.4.4.1-00011-QCARMSWP-2 api 6 features wowlan,ignore-otp crc32 727e5047
<3>ath10k_sdio mmc0:0001:1: failed to fetch board data for bus=sdio,vendor=0271,device=050a,subsystem-vendor=0000,subsystem-device=0000 from ath10k/QCA6174/hw3.0/board-2.bin
<6>ath10k_sdio mmc0:0001:1: board_file api 1 bmi_id N/A crc32 ed5f849a
<4>ath10k_sdio mmc0:0001:1: unsupported HTC service id: 1536
<6>ath10k_sdio mmc0:0001:1: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
<4>ath10k_sdio mmc0:0001:1: suspend timed out - target pause event never came
<4>mmc0: queuing unknown CIS tuple 0x01 (3 bytes)
<4>mmc0: queuing unknown CIS tuple 0x1a (5 bytes)
<4>mmc0: queuing unknown CIS tuple 0x1b (8 bytes)
<4>mmc0: queuing unknown CIS tuple 0x14 (0 bytes)
<4>ath10k_sdio mmc0:0001:1: unsupported HTC service id: 1536
<4>ath10k_sdio mmc0:0001:1: wmi command 135169 timeout, restarting hardware
<4>ath10k_sdio mmc0:0001:1: failed to enable adaptive qcs: -11
<4>ath10k_sdio mmc0:0001:1: could not suspend target (-108)
<4>mmc0: queuing unknown CIS tuple 0x01 (3 bytes)
<4>mmc0: queuing unknown CIS tuple 0x1a (5 bytes)
<4>mmc0: queuing unknown CIS tuple 0x1b (8 bytes)
<4>mmc0: queuing unknown CIS tuple 0x14 (0 bytes)
<4>ath10k_sdio mmc0:0001:1: cannot restart a device that hasn't been started
"""
I am using the correct FW files? Is anything else needed, maybe rename some file?
[1] https://github.com/kvalo/ath10k-firmware/blob/master/QCA6174/hw3.0
[2] https://kernel.googlesource.com/pub/scm/linux/kernel/git/kvalo/ath
reply other threads:[~2019-07-01 12:02 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=5D19F63D.8000302@digi.com \
--to=isaac.hermida@digi.com \
--cc=linux-wireless@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.