From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from s3.sipsolutions.net ([5.9.151.49]:37753 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752156AbcHIH4h (ORCPT ); Tue, 9 Aug 2016 03:56:37 -0400 Message-ID: <1470729393.28531.11.camel@sipsolutions.net> (sfid-20160809_095640_686085_07C122B5) Subject: Re: [PATCH v4] cfg80211: Provision to allow the support for different beacon intervals From: Johannes Berg To: "Undekari, Sunil Dutt" , "Kushwaha, Purushottam" Cc: "linux-wireless@vger.kernel.org" , "Malinen, Jouni" , "Kondabattini, Ganesh" , "Kalikot Veetil, Mahesh Kumar" , "Hullur Subramanyam, Amarnath" , "Kumar, Deepak (QCA)" Date: Tue, 09 Aug 2016 09:56:33 +0200 In-Reply-To: <9513d3caf9354aeda408f65128b4a079@aphydexm01f.ap.qualcomm.com> References: <1470374768-22297-1-git-send-email-pkushwah@qti.qualcomm.com> <1470386912.2977.28.camel@sipsolutions.net> <9513d3caf9354aeda408f65128b4a079@aphydexm01f.ap.qualcomm.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: > 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