From: Arend van Spriel <arend@broadcom.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: Janusz Dziedzic <janusz.dziedzic@tieto.com>,
<linux-wireless@vger.kernel.org>, <ath9k-devel@venema.h4ckr.net>,
"Felix Fietkau" <nbd@openwrt.org>, Jouni Malinen <j@w1.fi>
Subject: Re: [RFC] ath9k: advertise p2p dev support when chanctx
Date: Mon, 15 Jun 2015 20:19:02 +0200 [thread overview]
Message-ID: <557F1716.3040204@broadcom.com> (raw)
In-Reply-To: <21886.62363.946771.345441@gargle.gargle.HOWL>
+ Jouni
On 06/15/15 17:47, Sujith Manoharan wrote:
> Janusz Dziedzic wrote:
>>> At least the callbacks for adding/removing interfaces need
>>> to be handled ?
>>>
>> Strange, but I didn't hit any problem yet with my simple patch.
>
> Ok. But I am not very familiar with how p2p-device is supposed
> to be used...
The p2p-device is designed to be used for p2p discovery and p2p action
frame exchange. It make it easier for driver and/or firmware to
determine if user-space request is p2p related or not. However, in
discussions with Jouni I got the impression that ath (or qca) firmware
and/or drivers did not need this design. Not sure if that claim is
unaffected by the "use_chanctx=1" parameter.
Regards,
Arend
> Sujith
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-06-15 18:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 5:10 [RFC] ath9k: advertise p2p dev support when chanctx Janusz Dziedzic
2015-06-15 10:33 ` Sujith Manoharan
2015-06-15 11:38 ` Janusz Dziedzic
2015-06-15 11:46 ` Janusz Dziedzic
2015-06-15 15:47 ` Sujith Manoharan
2015-06-15 18:19 ` Arend van Spriel [this message]
2015-06-16 1:25 ` Sujith Manoharan
2015-06-16 6:30 ` Janusz Dziedzic
2015-06-16 7:08 ` Johannes Berg
2015-06-16 7:53 ` Sujith
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=557F1716.3040204@broadcom.com \
--to=arend@broadcom.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=j@w1.fi \
--cc=janusz.dziedzic@tieto.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=sujith@msujith.org \
/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).