From: Kalle Valo <kvalo@codeaurora.org>
To: Carl Huang <cjhuang@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
briannorris@chromium.org, dianders@chromium.org
Subject: Re: [PATCH v4 3/3] ath10k: allow dynamic SAR power limits via common API
Date: Mon, 18 Jan 2021 16:18:52 +0000 (UTC) [thread overview]
Message-ID: <20210118161852.E6222C433C6@smtp.codeaurora.org> (raw)
In-Reply-To: <20201203103728.3034-4-cjhuang@codeaurora.org>
Carl Huang <cjhuang@codeaurora.org> wrote:
> ath10k assigns ath10k_mac_set_sar_specs to ath10k_ops, and
> this function is called when user space application calls
> NL80211_CMD_SET_SAR_SPECS. ath10k also registers SAR type,
> and supported frequency ranges to wiphy so user space can
> query SAR capabilities.
>
> This SAR power limitation is compared to regulatory txpower
> and selects the minimal one to set when station is connected.
> Otherwise, it delays until the station is connected. If the
> station is disconnected, it returns to regulatory txpower.
>
> This feature is controlled by hw parameter: dynamic_sar_support.
>
> Tested-on: QCA6174 hw3.2 PCI WLAN.RM.4.4.1-00110-QCARMSWP-1
>
> Signed-off-by: Carl Huang <cjhuang@codeaurora.org>
> Reviewed-by: Brian Norris <briannorris@chromium.org>
> Reviewed-by: Abhishek Kumar <kuabhs@chromium.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
This added new warnings, I fixed them in the pending branch:
drivers/net/wireless/ath/ath10k/mac.c:84:1: warning: 'static' is not at beginning of declaration [-Wold-style-declaration]
drivers/net/wireless/ath/ath10k/mac.c:89:1: warning: 'static' is not at beginning of declaration [-Wold-style-declaration]
--
https://patchwork.kernel.org/project/linux-wireless/patch/20201203103728.3034-4-cjhuang@codeaurora.org/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-01-18 16:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 10:37 [PATCH v4 0/3] add common API to configure SAR Carl Huang
2020-12-03 10:37 ` Carl Huang
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 ` Carl Huang
2020-12-03 10:37 ` [PATCH v4 2/3] mac80211: add ieee80211_set_sar_specs Carl Huang
2020-12-03 10:37 ` 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 10:37 ` Carl Huang
2020-12-03 15:09 ` kernel test robot
2020-12-03 15:09 ` kernel test robot
2020-12-03 15:09 ` kernel test robot
2021-01-18 16:18 ` Kalle Valo [this message]
2021-01-18 16:18 ` Kalle Valo
2021-01-26 17:54 ` Kalle Valo
2021-01-26 17:54 ` Kalle Valo
2021-01-27 10:53 ` Kalle Valo
2021-01-27 10:53 ` Kalle Valo
2021-01-28 7:18 ` 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=20210118161852.E6222C433C6@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=briannorris@chromium.org \
--cc=cjhuang@codeaurora.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 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.