Hi Johannes, In another email, I am proposing to add an attribute for the source of interference (for example, "cellular") for each frequency range. So that way driver will have to specify exact source of interference and that would also avoid random channel steering. I would send out updated patch set with that change. Regards, Rajesh Chauhan -----Original Message----- From: Johannes Berg [mailto:johannes@xxxxxxxxxxxxxxxx] Sent: Monday, October 28, 2013 7:45 AM To: Chauhan, Rajesh Cc: linux-wireless@xxxxxxxxxxxxxxx; Rodriguez, Luis; Malinen, Jouni; Bahini, Henri; Chang, Leo; Luo, Xun Subject: Re: [PATCH] cfg80211/nl80211: Add support to report unsafe frequency ranges(s) On Thu, 2013-10-17 at 17:19 +0000, Chauhan, Rajesh wrote: > Hi Johannes, > > Thanks for your comment. Purpose of this patch is to add an API for > WLAN driver to report frequency ranges which should be avoided for > SAP/P2P-GO because of interference. > > How about if I reword commit test as below? > > cfg80211/nl80211: Add API to report frequency range(s) to be avoided > > Add support for WLAN driver to report frequency range(s) to be avoided > because of interference. Wouldn't it make more sense to raise a "detected interference" event? There's no way to know what channel range is affected anyway. I fear that this is vague enough for you to (ab)use it for all kinds of random "channel steering" from the driver. johannes ��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
