From: Wen Gong <wgong@codeaurora.org>
To: Justin Capella <justincapella@gmail.com>
Cc: ath10k <ath10k@lists.infradead.org>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v4 1/2] ath10k: add refcount for ath10k_core_restart
Date: Mon, 20 Jan 2020 21:34:00 +0800 [thread overview]
Message-ID: <7ad4db8ea256a823778edf89b2a1b2fc@codeaurora.org> (raw)
In-Reply-To: <CAMrEMU8DmXBGGU-WNd9bQAVVkHF6SCO7c_wv+dyH9D7KFOB8jw@mail.gmail.com>
On 2020-01-20 17:38, Justin Capella wrote:
> Ok thanks. I am still trying to familiarize myself with ath10k. A
> couple things come to mind:
>
> firstly recently there was a patch that set stations back to
> associated during recovery, do you know if the branch you're working
> against includes that? I will try to figure that out myself but it's
> at least worth considering.
>
can you give the patch link or patch?
> If I remember correctly, the sdio rx involves peeking and checking to
> see if the frame/packet continues/has more. In the case of firmware
> recovery/reconfig I think current code enables all sorts of debug
> pktlog stuff, historically it was maybe used as a hack to check for hw
> changes... But I mention it because I think what might be happening in
> some cases is fw crash follows a frame that would continue/extend,
> which is messing with the content and act_len (maybe?)
does it have relation with this patch?
>
> I also noticed that with aggregation I wind up getting a
> deauth/dissasoc followed by mlme delete sta/peer/key.
>
does it have relation with this patch?
> I think a retry count could be useful but what do you think of maybe
> using an event / timeout?
>
does it have relation with this patch?
>
>
next prev parent reply other threads:[~2020-01-20 13:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 3:19 [PATCH v4 0/2] start recovery process when payload length overflow for sdio Wen Gong
2020-01-08 3:19 ` [PATCH v4 1/2] ath10k: add refcount for ath10k_core_restart Wen Gong
2020-01-08 12:02 ` Justin Capella
2020-01-10 10:29 ` Wen Gong
2020-01-17 7:19 ` Wen Gong
2020-01-20 9:38 ` Justin Capella
2020-01-20 13:34 ` Wen Gong [this message]
2020-01-20 15:37 ` Justin Capella
2020-08-14 17:19 ` Kalle Valo
2020-08-18 8:39 ` Wen Gong
2020-09-07 15:52 ` Kalle Valo
2020-08-19 12:01 ` Wen Gong
2020-08-20 9:18 ` Wen Gong
2020-08-24 4:36 ` Wen Gong
2020-09-07 15:55 ` Kalle Valo
[not found] ` <871rjd37kz.fsf@codeaurora.org>
2020-09-08 3:47 ` Wen Gong
2020-01-08 3:19 ` [PATCH v4 2/2] ath10k: start recovery process when payload length exceeds max htc length for sdio Wen Gong
2020-08-14 15:37 ` 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=7ad4db8ea256a823778edf89b2a1b2fc@codeaurora.org \
--to=wgong@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=justincapella@gmail.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 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).