From: Johannes Berg <johannes@sipsolutions.net>
To: "Undekari, Sunil Dutt" <usdutt@qti.qualcomm.com>,
"Kushwaha, Purushottam" <pkushwah@qti.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Malinen, Jouni" <jouni@qca.qualcomm.com>,
"Kondabattini, Ganesh" <ganeshk@qti.qualcomm.com>,
"Kalikot Veetil, Mahesh Kumar" <mkalikot@qca.qualcomm.com>,
"Hullur Subramanyam, Amarnath" <amarnath@qca.qualcomm.com>,
"Kumar, Deepak (QCA)" <djindal@qti.qualcomm.com>
Subject: Re: [PATCH v4] cfg80211: Provision to allow the support for different beacon intervals
Date: Tue, 09 Aug 2016 09:56:33 +0200 [thread overview]
Message-ID: <1470729393.28531.11.camel@sipsolutions.net> (raw)
In-Reply-To: <9513d3caf9354aeda408f65128b4a079@aphydexm01f.ap.qualcomm.com>
> I guess , we can extend this to mesh and IBSS as well.
I don't know what your firmware/hardware capabilities are :)
> > It seems to me that if I were to specify beacon intervals which
> > have a very small GCD, you'll run into trouble when actually
> > sending beacons.
> > Perhaps there should be a requirement on the GCD?
> Can we have this published by the host drivers through a new wiphy
> parameter , say "min_diff_beacon_interval_multiplier". This set's the
> expectation that any different beacon intervals on the wiphy shall
> be a multiple of this parameter which is advertised by the host
> driver , isn't ?
>
I'd argue that instead of having the interface combinations flag, that
nl80211 attribute could carry the GCD?
johannes
next prev parent reply other threads:[~2016-08-09 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 5:26 [PATCH v4] cfg80211: Provision to allow the support for different beacon intervals Purushottam Kushwaha
2016-08-05 8:48 ` Johannes Berg
2016-08-08 17:58 ` Undekari, Sunil Dutt
2016-08-09 7:56 ` Johannes Berg [this message]
2016-08-10 14:53 ` Undekari, Sunil Dutt
2016-08-10 15:18 ` 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=1470729393.28531.11.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=amarnath@qca.qualcomm.com \
--cc=djindal@qti.qualcomm.com \
--cc=ganeshk@qti.qualcomm.com \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mkalikot@qca.qualcomm.com \
--cc=pkushwah@qti.qualcomm.com \
--cc=usdutt@qti.qualcomm.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).