linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: linux-wireless@vger.kernel.org
Subject: nl80211 vendor commands on upstream drivers
Date: Fri, 12 May 2017 16:51:52 +0300	[thread overview]
Message-ID: <87wp9mp4hz.fsf@kamboji.qca.qualcomm.com> (raw)

Hi,

last fall at Wireless Summit at Santa Fe we talked about having nl80211
vendor commands in upstream drivers[1]. The discussion starter was this
wil6210 patch:

wil6210: low level RF sector API
https://patchwork.kernel.org/patch/9403071/

The conclusion from the discussion was that in some (rare) cases having
vendor commands in upstream is acceptable, for example like here when
interfacing low level hw features which most likely is not not
compatible with other designs.

But this does not mean that the gates are open for all possible hacks
via vendor commands, we still want to have generic nl80211 interface for
all normal functionality. Just to give some examples of something which
is NOT acceptable:

* yet another scanning interface (exception maybe being spectral scan?)
* power save settings
* btcoex settings

Comments? Am I forgetting something from the discussion?

[1] https://docs.google.com/document/u/1/d/e/2PACX-1vQXbVQ-3zQt3Bcr3OWfwzbw_C49tTvf0ed8Hmf7b20E6tXc3a40tWZmPku49iGDE-OhgxNmO_lkkHEn/pub

-- 
Kalle Valo

             reply	other threads:[~2017-05-12 13:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12 13:51 Kalle Valo [this message]
2017-05-17 13:34 ` nl80211 vendor commands on upstream drivers Johannes Berg
2017-05-18  6:40   ` Kalle Valo

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=87wp9mp4hz.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.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).