From: Kalle Valo <kvalo@codeaurora.org>
To: ojab <ojab@ojab.ru>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, ojab <ojab@ojab.ru>,
ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] ath10k: don't fail if IRAM write fails
Date: Wed, 20 Oct 2021 07:54:25 +0000 (UTC) [thread overview]
Message-ID: <163471645955.23156.7506403648173685920.kvalo@codeaurora.org> (raw)
In-Reply-To: <20210722193459.7474-1-ojab@ojab.ru>
ojab <ojab@ojab.ru> wrote:
> After reboot with kernel & firmware updates I found `failed to copy
> target iram contents:` in dmesg and missing wlan interfaces for both
> of my QCA9984 compex cards. Rolling back kernel/firmware didn't fixed
> it, so while I have no idea what's actually happening, I don't see why
> we should fail in this case, looks like some optional firmware ability
> that could be skipped.
>
> Also with additional logging there is
> ```
> [ 6.839858] ath10k_pci 0000:04:00.0: No hardware memory
> [ 6.841205] ath10k_pci 0000:04:00.0: failed to copy target iram contents: -12
> [ 6.873578] ath10k_pci 0000:07:00.0: No hardware memory
> [ 6.875052] ath10k_pci 0000:07:00.0: failed to copy target iram contents: -12
> ```
> so exact branch could be seen.
>
> Signed-off-by: Slava Kardakov <ojab@ojab.ru>
> Tested-by: Axel Rasmussen <axelrasmussen@google.com>
I'm planning to take this patch instead:
https://patchwork.kernel.org/project/linux-wireless/patch/20211020075054.23061-1-kvalo@codeaurora.org/
Patch set to Superseded.
--
https://patchwork.kernel.org/project/linux-wireless/patch/20210722193459.7474-1-ojab@ojab.ru/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: ojab <ojab@ojab.ru>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, ojab <ojab@ojab.ru>,
ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] ath10k: don't fail if IRAM write fails
Date: Wed, 20 Oct 2021 07:54:25 +0000 (UTC) [thread overview]
Message-ID: <163471645955.23156.7506403648173685920.kvalo@codeaurora.org> (raw)
In-Reply-To: <20210722193459.7474-1-ojab@ojab.ru>
ojab <ojab@ojab.ru> wrote:
> After reboot with kernel & firmware updates I found `failed to copy
> target iram contents:` in dmesg and missing wlan interfaces for both
> of my QCA9984 compex cards. Rolling back kernel/firmware didn't fixed
> it, so while I have no idea what's actually happening, I don't see why
> we should fail in this case, looks like some optional firmware ability
> that could be skipped.
>
> Also with additional logging there is
> ```
> [ 6.839858] ath10k_pci 0000:04:00.0: No hardware memory
> [ 6.841205] ath10k_pci 0000:04:00.0: failed to copy target iram contents: -12
> [ 6.873578] ath10k_pci 0000:07:00.0: No hardware memory
> [ 6.875052] ath10k_pci 0000:07:00.0: failed to copy target iram contents: -12
> ```
> so exact branch could be seen.
>
> Signed-off-by: Slava Kardakov <ojab@ojab.ru>
> Tested-by: Axel Rasmussen <axelrasmussen@google.com>
I'm planning to take this patch instead:
https://patchwork.kernel.org/project/linux-wireless/patch/20211020075054.23061-1-kvalo@codeaurora.org/
Patch set to Superseded.
--
https://patchwork.kernel.org/project/linux-wireless/patch/20210722193459.7474-1-ojab@ojab.ru/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2021-10-20 7:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 19:35 [PATCH V2] ath10k: don't fail if IRAM write fails ojab
2021-07-22 19:35 ` ojab
2021-07-22 19:42 ` ojab //
2021-07-22 19:42 ` ojab //
2021-08-02 2:23 ` Axel Rasmussen
2021-08-02 2:23 ` Axel Rasmussen
2021-08-12 20:21 ` Axel Rasmussen
2021-08-12 20:21 ` Axel Rasmussen
2021-08-14 11:33 ` sparks71
2021-08-14 11:33 ` sparks71
2021-08-25 16:15 ` ojab //
2021-08-25 16:15 ` ojab //
2021-09-08 23:42 ` ojab //
2021-09-08 23:42 ` ojab //
2021-09-17 19:30 ` ojab //
2021-09-17 19:30 ` ojab //
2021-09-18 10:12 ` sparks71
2021-09-18 10:12 ` sparks71
2021-09-18 11:21 ` ojab //
2021-09-18 11:21 ` ojab //
2021-09-21 7:29 ` Kalle Valo
2021-09-21 7:29 ` Kalle Valo
2021-09-21 7:50 ` sparks71
2021-09-21 7:50 ` sparks71
2021-10-20 7:54 ` Kalle Valo [this message]
2021-10-20 7:54 ` Kalle Valo
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=163471645955.23156.7506403648173685920.kvalo@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ojab@ojab.ru \
/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.