linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
To: "Peer, Ilan" <ilan.peer@intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>,
	"John W . Linville" <linville@tuxdriver.com>,
	Jouni Malinen <jouni@qca.qualcomm.com>
Subject: Re: [PATCH v10 2/2] cfg80211: P2P find phase offload
Date: Tue, 25 Jun 2013 12:25:00 +0300	[thread overview]
Message-ID: <1489286.dFNgzINo7e@lx-vladimir> (raw)
In-Reply-To: <CB3B3D4774441E42AA3EA0E1BA8230A01AD22795@HASMSX106.ger.corp.intel.com>

On Tuesday, June 25, 2013 07:06:28 AM Peer, Ilan wrote:
> > + * @listen_channel: channels to listen on; not NULL
> 
> s/channels/channel/  (only a single listen channel)
Sure, thanks

<skip>
> Just to clarify something: even if the driver reports that it supports probe response offloading, can wpas choose not to use this capability and handle all the probe requests on its own (at least for debugging)? For example in case that the probe response IE len is zero, the driver can deduce the it should not respond to probe requests.

Problem is, some hardware do not let you to do so; it simply replies by itself.
NL80211_FEATURE_P2P_PROBE_RESP_OFFLOAD indicates device __can__ answer. From this,
wpa_s can conclude it may be answered by device probes that is may see or not.
It is out of scope for this commit to specify how to tell to the device to not answer
(I suppose to use debugfs for this)

> 
> > @@ -1740,6 +1748,10 @@ enum nl80211_attrs {
> > 
> >  	NL80211_ATTR_RXMGMT_FLAGS,
> > 
> > +	NL80211_ATTR_MIN_DISCOVERABLE_INTERVAL,
> > +	NL80211_ATTR_MAX_DISCOVERABLE_INTERVAL,
> > +	NL80211_ATTR_LISTEN_FREQ,
> 
> You can use NL80211_ATTR_WIPHY_FREQ

OK, will do so.

> 
> > +TRACE_EVENT(rdev_start_p2p_find,
> > +	TP_PROTO(struct wiphy *wiphy, struct wireless_dev *wdev,
> > +		 struct cfg80211_p2p_find_params *params),
> > +	TP_ARGS(wiphy, wdev, params),
> > +	TP_STRUCT__entry(
> > +		WIPHY_ENTRY
> > +		WDEV_ENTRY
> > +		__field(u32, min_di)
> > +		__field(u32, max_di)
> > +		__field(int, n_channels)
> 
> Can you also add here the listen channel?

Sure

Thanks, Vladimir

      reply	other threads:[~2013-06-25  9:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24  8:49 [PATCH v10 0/2] P2P find phase offload Vladimir Kondratiev
2013-06-24  8:49 ` [PATCH v10 1/2] cfg80211: add flags to cfg80211_rx_mgmt Vladimir Kondratiev
2013-06-24 13:46   ` Arend van Spriel
2013-06-24 14:08   ` Johannes Berg
2013-06-24  8:49 ` [PATCH v10 2/2] cfg80211: P2P find phase offload Vladimir Kondratiev
2013-06-25  7:06   ` Peer, Ilan
2013-06-25  9:25     ` Vladimir Kondratiev [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=1489286.dFNgzINo7e@lx-vladimir \
    --to=qca_vkondrat@qca.qualcomm.com \
    --cc=ilan.peer@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=jouni@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rodrigue@qca.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).