From: Carl Huang <cjhuang@codeaurora.org>
To: ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, briannorris@chromium.org,
dianders@chromium.org
Subject: [PATCH v4 0/3] add common API to configure SAR
Date: Thu, 3 Dec 2020 05:37:25 -0500 [thread overview]
Message-ID: <20201203103728.3034-1-cjhuang@codeaurora.org> (raw)
This patchset is to add common API to configure SAR.
The mechanism is wlan driver registers sar capability
to wiphy and userspace queries it. Userspace then sets
power limiation to wlan driver.
v4:
- add "Reviewed-by:" tag
v3:
- check index duplicates. If index duplicates, returns error
v2:
- rebased on ToT
- fix comments by Johannes and Abhishek
- change sar_power to s32 and range_index to u32
Carl Huang (3):
nl80211: add common API to configure SAR power limitations.
mac80211: add ieee80211_set_sar_specs
ath10k: allow dynamic SAR power limits via common API
drivers/net/wireless/ath/ath10k/core.c | 16 +++
drivers/net/wireless/ath/ath10k/core.h | 3 +
drivers/net/wireless/ath/ath10k/hw.h | 2 +
drivers/net/wireless/ath/ath10k/mac.c | 225 ++++++++++++++++++++++++---------
include/net/cfg80211.h | 51 ++++++++
include/net/mac80211.h | 2 +
include/uapi/linux/nl80211.h | 102 +++++++++++++++
net/mac80211/cfg.c | 12 ++
net/wireless/nl80211.c | 185 +++++++++++++++++++++++++++
net/wireless/rdev-ops.h | 12 ++
net/wireless/trace.h | 19 +++
11 files changed, 570 insertions(+), 59 deletions(-)
--
2.7.4
next reply other threads:[~2020-12-03 10:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 10:37 Carl Huang [this message]
2020-12-03 10:37 ` [PATCH v4 1/3] nl80211: add common API to configure SAR power limitations Carl Huang
2020-12-03 10:37 ` [PATCH v4 2/3] mac80211: add ieee80211_set_sar_specs Carl Huang
2020-12-03 10:37 ` [PATCH v4 3/3] ath10k: allow dynamic SAR power limits via common API Carl Huang
2020-12-03 15:09 ` kernel test robot
2021-01-18 16:18 ` Kalle Valo
2021-01-26 17:54 ` Kalle Valo
2021-01-27 10:53 ` Kalle Valo
2021-01-28 7:18 ` 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=20201203103728.3034-1-cjhuang@codeaurora.org \
--to=cjhuang@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.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).