From: Fabio Estevam <festevam@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>, wgong@codeaurora.org
Cc: erik.stromdahl@gmail.com, niklas.cassel@wdc.com,
ath10k@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>,
alagusankar@silex-india.com
Subject: ath10k_sdio: failed to write to address
Date: Fri, 17 Sep 2021 14:37:52 -0300 [thread overview]
Message-ID: <CAOMZO5BROh1wET6vcif_8Q+aMQUFqRMP5uttBBLV8nJnbOv8rg@mail.gmail.com> (raw)
Hi,
On an i.MX7-based board, I see the following "failed to write to address" error:
ath10k_sdio mmc2:0001:1: qca9377 hw1.1 sdio target 0x05020001 chip_id
0x00000000 sub 0000:0000
ath10k_sdio mmc2:0001:1: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
ath10k_sdio mmc2:0001:1: firmware ver WLAN.TF.1.1.1-00061-QCATFSWPZ-1
api 5 features ignore-otp crc32 7746e551
EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
ath10k_sdio mmc2:0001:1: failed to fetch board data for
bus=sdio,vendor=0271,device=0701,subsystem-vendor=0000,subsystem-device=0000
from ath10k/QCA9377/hw1.0/board-2.bin
ath10k_sdio mmc2:0001:1: board_file api 1 bmi_id N/A crc32 544289f7
ath10k_sdio mmc2:0001:1: htt-ver 3.32 wmi-op 4 htt-op 3 cal otp
max-sta 32 raw 0 hwcrypto 1
ath10k_sdio mmc2:0001:1: failed to write to address 0x12ff5: -84
ath10k_sdio mmc2:0001:1: failed to write skb to 0x12ff5 asynchronously: -84
The wifi is functional despite the errors.
I tried applying Erik's patch:
https://github.com/erstrom/linux-ath/commit/6507fd8df431e1d1f1ea344224956387dc1d35aa
and the one from Niklas:
https://github.com/erstrom/linux-ath/commit/4e794a12fa89e353e38528d1ada5d86f19672c3c
but it did not help.
Does anyone have any suggestions as to how to fix it?
Thanks,
Fabio Estevam
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
reply other threads:[~2021-09-17 17:38 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=CAOMZO5BROh1wET6vcif_8Q+aMQUFqRMP5uttBBLV8nJnbOv8rg@mail.gmail.com \
--to=festevam@gmail.com \
--cc=alagusankar@silex-india.com \
--cc=ath10k@lists.infradead.org \
--cc=erik.stromdahl@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=niklas.cassel@wdc.com \
--cc=wgong@codeaurora.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).