From: Ben Greear <greearb@candelatech.com>
To: Youghandhar Chintala <youghand@codeaurora.org>,
johannes@sipsolutions.net, ath10k@lists.infradead.org
Cc: kuabhs@chromium.org, netdev@vger.kernel.org,
briannorris@chromium.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, dianders@chromium.org,
pillair@codeaurora.org, kuba@kernel.org, davem@davemloft.net,
kvalo@codeaurora.org
Subject: Re: [PATCH 0/3] mac80211: Trigger disconnect for STA during recovery
Date: Tue, 15 Dec 2020 10:23:33 -0800 [thread overview]
Message-ID: <18dfa52b-5edd-f737-49c9-f532c1c10ba2@candelatech.com> (raw)
In-Reply-To: <20201215172113.5038-1-youghand@codeaurora.org>
On 12/15/20 9:21 AM, Youghandhar Chintala wrote:
> From: Rakesh Pillai <pillair@codeaurora.org>
>
> Currently in case of target hardware restart ,we just reconfig and
> re-enable the security keys and enable the network queues to start
> data traffic back from where it was interrupted.
Are there any known mac80211 radios/drivers that *can* support seamless restarts?
If not, then just could always enable this feature in mac80211?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2020-12-15 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 17:21 [PATCH 0/3] mac80211: Trigger disconnect for STA during recovery Youghandhar Chintala
2020-12-15 18:23 ` Ben Greear [this message]
2020-12-16 11:35 ` Rakesh Pillai
2020-12-17 22:24 ` Brian Norris
2020-12-17 22:57 ` Ben Greear
2020-12-17 23:18 ` Brian Norris
2020-12-17 22:30 ` Brian Norris
2020-12-15 17:30 Youghandhar Chintala
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=18dfa52b-5edd-f737-49c9-f532c1c10ba2@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=briannorris@chromium.org \
--cc=davem@davemloft.net \
--cc=dianders@chromium.org \
--cc=johannes@sipsolutions.net \
--cc=kuabhs@chromium.org \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pillair@codeaurora.org \
--cc=youghand@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).