All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: <tony0620emma@gmail.com>, <linux-wireless@vger.kernel.org>,
	<kevin_yang@realtek.com>
Subject: Re: [PATCH] rtw88: support SAR via kernel common API
Date: Mon, 20 Dec 2021 11:48:04 +0200	[thread overview]
Message-ID: <875yrjboa3.fsf@codeaurora.org> (raw)
In-Reply-To: <20211220093656.65312-1-pkshih@realtek.com> (Ping-Ke Shih's message of "Mon, 20 Dec 2021 17:36:56 +0800")

Ping-Ke Shih <pkshih@realtek.com> writes:

> From: Zong-Zhe Yang <kevin_yang@realtek.com>
>
> Register cfg80211_sar_capa with type NL80211_SAR_TYPE_POWER and four
> frequency ranges for configurations in unit of 0.25 dBm. And handle
> callback set_sar_specs.
>
> Originally, TX power has three main parameters, i.e. power base,
> power by rate, and power limit. The formula can be simply considered
> as TX power = power base + min(power by rate, power limit). With the
> support of SAR which can be treated as another power limit, there is
> one more parameter for TX power. And the formula will evolve into
> TX power = power base + min(power by rate, power limit, power sar).
>
> Besides, debugfs tx_pwr_tbl is also refined to show SAR information.
> The following is an example for the difference.
> Before supporting SAR,
> -----------------------------------
> ...
> path rate       pwr       base      (byr  lmt ) rem
>    A  CCK_1M     66(0x42)   78  -12 (  12  -12)    0
>    A  CCK_2M     66(0x42)   78  -12 (   8  -12)    0
> ...
> -----------------------------------
> After supporting SAR and making some configurations,
> -----------------------------------
> ...
> path rate       pwr       base      (byr  lmt  sar ) rem
>    A  CCK_1M     62(0x3e)   78  -16 (  12  -12  -16)    0
>    A  CCK_2M     62(0x3e)   78  -16 (   8  -12  -16)    0
> ...
> -----------------------------------
>
> Signed-off-by: Zong-Zhe Yang <kevin_yang@realtek.com>
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>

I switched my email to kvalo@kernel.org and my codeaurora.org address
will stop working soon, please update your address book and scripts.

No need to resend because of this.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2021-12-20  9:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20  9:36 [PATCH] rtw88: support SAR via kernel common API Ping-Ke Shih
2021-12-20  9:48 ` Kalle Valo [this message]
2021-12-21 18:22 ` 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=875yrjboa3.fsf@codeaurora.org \
    --to=kvalo@kernel.org \
    --cc=kevin_yang@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=tony0620emma@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.