Linux wireless drivers development
 help / color / mirror / Atom feed
From: James Prestwood <james.prestwood@linux.intel.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: ROC event when CMD_FRAME duration expires
Date: Wed, 12 Jun 2019 12:18:25 -0700	[thread overview]
Message-ID: <f7ac0d5ebf9c3e863576c63b374b07a8e3f689b7.camel@linux.intel.com> (raw)
In-Reply-To: <292712d7505871a093bd596d2e03ec7d811370f9.camel@sipsolutions.net>

On Wed, 2019-06-12 at 21:11 +0200, Johannes Berg wrote:
> On Tue, 2019-06-11 at 13:51 -0700, James Prestwood wrote:
> > Hi,
> > 
> > I see that the event CMD_CANCEL_REMAIN_ON_CHANNEL is emitted when a
> > CMD_REMAIN_ON_CHANNEL duration expires, but this is not true for
> > CMD_FRAME when sending offchannel and providing a duration. I see
> > wpa_supplicant handles this with its own timeout, but couldn't the
> > same
> > event be emitted for CMD_FRAME if the duration expires?
> 
> I guess? I guess this is for a case where you actually have a wait
> after
> the TX, for waiting for a response?

Yes exactly. For example a GAS/ANQP request before association to some
offchannel AP (that's at least our use case).

Thanks,
James
> 
> johannes
> 


  reply	other threads:[~2019-06-12 19:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 20:51 ROC event when CMD_FRAME duration expires James Prestwood
2019-06-12 19:11 ` Johannes Berg
2019-06-12 19:18   ` James Prestwood [this message]
2019-06-12 19:31     ` Johannes Berg

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=f7ac0d5ebf9c3e863576c63b374b07a8e3f689b7.camel@linux.intel.com \
    --to=james.prestwood@linux.intel.com \
    --cc=johannes@sipsolutions.net \
    --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