linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rajkumar Manoharan <rmanohar@codeaurora.org>
To: John Crispin <john@phrozen.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Kalle Valo <kvalo@codeaurora.org>,
	Srini Kode <skode@qti.qualcomm.com>,
	Rajkumar Manoharan <rmanohar@qti.qualcomm.com>,
	linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
	Shashidhar Lakkavalli <slakkavalli@datto.com>,
	linux-wireless-owner@vger.kernel.org
Subject: Re: [PATCH V2 2/3] mac80211: dynamically turn TWT requester support on and off
Date: Mon, 29 Apr 2019 23:45:17 -0700	[thread overview]
Message-ID: <a580242a242ec6126928bba5227f1e2d@codeaurora.org> (raw)
In-Reply-To: <20190426094150.18078-3-john@phrozen.org>

On 2019-04-26 02:41, John Crispin wrote:
> Turn TWT on/off for STA interfaces when they associate and/or receive a
> beacon where the twt_responder bit has changed.
> 

Does it mean that TWT responder can be turn on/off when AP is UP and 
running?
I thought any change in beacon needs AP restart. no?

-Rajkumar

  reply	other threads:[~2019-04-30  6:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26  9:41 [PATCH V2 0/3] mac80211: notify the driver when it should enable TWT John Crispin
2019-04-26  9:41 ` [PATCH V2 1/3] mac80211: allow turning TWT responder support on and off via netlink John Crispin
2019-04-26 19:50   ` John Crispin
2019-04-26 19:51     ` Johannes Berg
2019-04-26 19:53       ` John Crispin
2019-04-30  6:42   ` Rajkumar Manoharan
2019-04-26  9:41 ` [PATCH V2 2/3] mac80211: dynamically turn TWT requester support on and off John Crispin
2019-04-30  6:45   ` Rajkumar Manoharan [this message]
2019-04-30  6:58     ` John Crispin
2019-04-26  9:41 ` [PATCH V2 3/3] ath11k: add TWT support John Crispin
2019-04-30  6:50   ` Rajkumar Manoharan

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=a580242a242ec6126928bba5227f1e2d@codeaurora.org \
    --to=rmanohar@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=john@phrozen.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless-owner@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rmanohar@qti.qualcomm.com \
    --cc=skode@qti.qualcomm.com \
    --cc=slakkavalli@datto.com \
    /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).