All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
	Maharaja Kennadyrajan <mkenna@codeaurora.org>
Cc: Maharaja Kennadyrajan <mkenna@codeaurora.org>
Subject: Re: [PATCH 1/3] nl80211: Add support for beacon tx mode
Date: Mon, 22 Feb 2021 11:32:43 +0100	[thread overview]
Message-ID: <2718995.X0rUDs3ZmB@ripper> (raw)
In-Reply-To: <1613988573-10839-2-git-send-email-mkenna@codeaurora.org>


[-- Attachment #1.1: Type: text/plain, Size: 550 bytes --]

On Monday, 22 February 2021 11:09:31 CET Maharaja Kennadyrajan wrote:
> User can configure the beacon tx mode while bring-up the AP
> or MESH. Hence, added the support in the nl80211/cfg80211
> layer to honour the beacon tx mode configuration and pass
> this value to the driver.

There is not a definition what this actually means. But I am guessing that you 
are mean the way the HW sends our the beacons for a multivif (beaconing) 
setup. And in this case, it is a per "phy" setting and not a per AP/meshpoint 
setting, right?

Kind regards,
	Sven

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 102 bytes --]

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven@narfation.org>
To: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
	Maharaja Kennadyrajan <mkenna@codeaurora.org>
Cc: Maharaja Kennadyrajan <mkenna@codeaurora.org>
Subject: Re: [PATCH 1/3] nl80211: Add support for beacon tx mode
Date: Mon, 22 Feb 2021 11:32:43 +0100	[thread overview]
Message-ID: <2718995.X0rUDs3ZmB@ripper> (raw)
In-Reply-To: <1613988573-10839-2-git-send-email-mkenna@codeaurora.org>

[-- Attachment #1: Type: text/plain, Size: 550 bytes --]

On Monday, 22 February 2021 11:09:31 CET Maharaja Kennadyrajan wrote:
> User can configure the beacon tx mode while bring-up the AP
> or MESH. Hence, added the support in the nl80211/cfg80211
> layer to honour the beacon tx mode configuration and pass
> this value to the driver.

There is not a definition what this actually means. But I am guessing that you 
are mean the way the HW sends our the beacons for a multivif (beaconing) 
setup. And in this case, it is a per "phy" setting and not a per AP/meshpoint 
setting, right?

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-02-22 19:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 10:09 [PATCH 0/3] Add support to configure beacon tx mode Maharaja Kennadyrajan
2021-02-22 10:09 ` Maharaja Kennadyrajan
2021-02-22 10:09 ` [PATCH 1/3] nl80211: Add support for " Maharaja Kennadyrajan
2021-02-22 10:09   ` Maharaja Kennadyrajan
2021-02-22 10:32   ` Sven Eckelmann [this message]
2021-02-22 10:32     ` Sven Eckelmann
2021-04-08 11:11     ` Johannes Berg
2021-04-08 11:11       ` Johannes Berg
2021-02-22 10:09 ` [PATCH 2/3] mac80211: " Maharaja Kennadyrajan
2021-02-22 10:09   ` Maharaja Kennadyrajan
2021-02-22 10:09 ` [PATCH 3/3] ath11k: " Maharaja Kennadyrajan
2021-02-22 10:09   ` Maharaja Kennadyrajan

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=2718995.X0rUDs3ZmB@ripper \
    --to=sven@narfation.org \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mkenna@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.