linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maharaja Kennadyrajan <mkenna@codeaurora.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Add support to configure beacon tx mode
Date: Wed, 26 May 2021 19:43:40 +0530	[thread overview]
Message-ID: <4038b2868605da158392bd4c65d10c66@codeaurora.org> (raw)
In-Reply-To: <4581459.tLtf2NohVe@ripper>

On 2021-04-30 12:45, Sven Eckelmann wrote:
> On Thursday, 29 April 2021 13:47:51 CEST Maharaja Kennadyrajan wrote:
> [...]
>> Beacons can be sent out in burst(continuously in a single shot
>> one after another) or staggered (equally spread out over beacon
>> interval) mode.
>> 
>> V2:
>> 	Addressed Johannes's comment on v1 patch.
>> 	Updated the commit log.
> 
> Still it is advertised as vif setting but the code itself shows that it 
> is a
> phy setting (as you would expect). Or is it a potential feature for a 
> device
> to send some beacons staggered and some beacons as burst?

[Maha]: No, it won't allow to send some beacons in staggered and some 
beacons in burst
mode. It will send either staggered or burst mode at a time in a device.

> Kind regards,
> 	Sven

      reply	other threads:[~2021-05-26 14:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 11:47 [PATCH v2 0/3] Add support to configure beacon tx mode Maharaja Kennadyrajan
2021-04-29 11:47 ` [PATCH v2 1/3] nl80211: Add support for " Maharaja Kennadyrajan
2021-05-03 17:24   ` jjohnson
2021-05-05  7:18     ` Maharaja Kennadyrajan
2021-05-05 14:27       ` jjohnson
2021-04-29 11:47 ` [PATCH v2 2/3] mac80211: " Maharaja Kennadyrajan
2021-04-29 11:47 ` [PATCH v2 3/3] ath11k: " Maharaja Kennadyrajan
2021-04-30  7:15 ` [PATCH v2 0/3] Add support to configure " Sven Eckelmann
2021-05-26 14:13   ` Maharaja Kennadyrajan [this message]

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=4038b2868605da158392bd4c65d10c66@codeaurora.org \
    --to=mkenna@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sven@narfation.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).