From: Johannes Berg <johannes@sipsolutions.net>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Cc: "Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>,
Jouni Malinen <jouni@qca.qualcomm.com>,
"John W . Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [RFC] P2P find offload
Date: Fri, 15 Mar 2013 19:40:23 +0100 [thread overview]
Message-ID: <1363372823.8656.41.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <2799886.P5v870j3h2@lx-vladimir>
> Allow to implement P2P find phase in the driver/firmware.
>
> Offload scheme designed as follows:
>
> - Driver provide methods start_p2p_find and stop_p2p_find in the cfg80211_ops;
> indicates support for p2p find offload by setting feature
> NL80211_FEATURE_P2P_FIND_OFFLOAD
Why not just indicate the command presence rather than a feature flag?
> - perform legacy scan, through driver's cfg80211_ops 'scan' method
Why the legacy scan? btw this is what I was worried about -- this API
robs us of the ability to do "progressive" p2p scan.
> - configure rx management filter to get probe-request and probe-response frames
Interesting, so this is pretty much bypassing the scan BSS table
mechanism. I guess it makes sense though.
> - driver start p2p find with hardware and notify wpa_supplicant with
> cfg80211_p2p_find_notify(NL80211_CMD_START_P2P_FIND)
See other mail -- is that really useful?
> cfg80211_p2p_find_notify(NL80211_CMD_STOP_P2P_FIND)
btw, if both are needed I'd prefer not to give a command number here,
it's useless to give anything else and this is a bit confusing.
> /**
> + * struct cfg80211_p2p_find_params - parameters for P2P find
> + * @probe_ie: IE's for probe frames
probe request, presumably?
Also, this is probably *additional* IEs, i.e. supported rates etc. are
expected to be created by the driver?
> + * @probe_resp_ie: IE's for probe response frames
similarly here?
> + * @probe_resp_ie_len: length, bytes, of @probe_resp_ie
> + * @min_discoverable_interval and
need : otherwise it's not valid kernel-doc
> + * @NL80211_ATTR_MIN_DISCOVERABLE_INTERVAL,
same here
> + genlmsg_multicast_netns(wiphy_net(&rdev->wiphy), msg, 0,
> + nl80211_scan_mcgrp.id, GFP_KERNEL);
indentation
> +static inline int rdev_start_p2p_find(struct cfg80211_registered_device *rdev,
> + struct wireless_dev *wdev,
> + struct cfg80211_p2p_find_params *params)
indentation
> +static inline void rdev_stop_p2p_find(struct cfg80211_registered_device *rdev,
> + struct wireless_dev *wdev)
ditto
> + TP_PROTO(struct wiphy *wiphy, struct wireless_dev *wdev,
> + struct cfg80211_p2p_find_params *params),
ditto
> + TP_printk(WDEV_PR_FMT ", cmd: %d", WDEV_PR_ARG,
> + __entry->cmd)
ditto
johannes
next prev parent reply other threads:[~2013-03-16 12:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 12:24 [RFC] P2P find offload Vladimir Kondratiev
2013-03-04 15:47 ` Johannes Berg
2013-03-07 7:10 ` Vladimir Kondratiev
2013-03-07 9:31 ` Vladimir Kondratiev
2013-03-07 10:08 ` Johannes Berg
2013-03-07 10:11 ` Johannes Berg
2013-03-07 14:10 ` Vladimir Kondratiev
2013-03-10 15:43 ` Vladimir Kondratiev
2013-03-15 18:40 ` Johannes Berg [this message]
2013-03-17 8:56 ` Vladimir Kondratiev
2013-03-18 20:31 ` Johannes Berg
[not found] ` <3959922.dEpYdEMVAq@lx-vladimir>
2013-03-19 20:27 ` Johannes Berg
2013-03-15 15:51 ` Johannes Berg
2013-03-07 10:01 ` 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=1363372823.8656.41.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=qca_vkondrat@qca.qualcomm.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