All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Ujjal Roy <royujjal@gmail.com>,
	Johannes Berg <johannes@sipsolutions.net>
Cc: Kernel <linux-wireless@vger.kernel.org>
Subject: Re: P2P_DEVICE support in driver
Date: Wed, 18 Dec 2013 12:01:20 +0100	[thread overview]
Message-ID: <52B18080.7070709@broadcom.com> (raw)
In-Reply-To: <CAE2MWkn5KT7nM+RgPptbfUDVEz5KThytpNmMUzhQeP30ZSocEg@mail.gmail.com>

On 12/18/2013 11:29 AM, Ujjal Roy wrote:
> Hi Johannes,
> 
> I want to add P2P_DEVICE support in a driver. And it's not described
> in the P2P spec. So, please tell me the following points -
> 1> what do the driver do?
> 2> register_netdevice() should not be called from driver for the
> P2P_DEVICE interface. Then what are the procedures (network stacks) to
> add a P2P device from driver's point of view?
> 3> How the supplicant will communicate with this type of interface?
> 

Hi Ujjal,

P2P_DEVICE interface is meant for the P2P discovery phase, which is in
the P2P spec. It is also depending on the driver/firmware whether it
needs this to distinguish between a regular scan and P2P scan. Some
vendors who did have that need created a 'dummy' netdev for that purpose
although it is only used for scanning/listening, ie. no network traffic.
To avoid that waste the P2P_DEVICE interface was cooked up. The
P2P_DEVICE interface is created through nl80211 by recent wpa_supplicant
when driver indicates support.

Regards,
Arend

      parent reply	other threads:[~2013-12-18 11:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 10:29 P2P_DEVICE support in driver Ujjal Roy
2013-12-18 10:46 ` Johannes Berg
2013-12-18 11:01 ` Arend van Spriel [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=52B18080.7070709@broadcom.com \
    --to=arend@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=royujjal@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.