From: Felix Fietkau <nbd@openwrt.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 2/2] mac80211: add support for per-chain signal strength reporting
Date: Mon, 22 Apr 2013 16:53:04 +0200 [thread overview]
Message-ID: <51754ED0.5080106@openwrt.org> (raw)
In-Reply-To: <1366641428.8637.31.camel@jlt4.sipsolutions.net>
On 2013-04-22 4:37 PM, Johannes Berg wrote:
> On Mon, 2013-04-22 at 16:29 +0200, Felix Fietkau wrote:
>> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
>> ---
>> include/net/mac80211.h | 5 +++++
>> net/mac80211/cfg.c | 13 ++++++++++++-
>> net/mac80211/rx.c | 14 ++++++++++++++
>> net/mac80211/sta_info.c | 2 ++
>> net/mac80211/sta_info.h | 5 +++++
>> 5 files changed, 38 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/net/mac80211.h b/include/net/mac80211.h
>> index 4ecff78..aeb4a5c 100644
>> --- a/include/net/mac80211.h
>> +++ b/include/net/mac80211.h
>> @@ -848,6 +848,9 @@ enum mac80211_rx_flags {
>> * @signal: signal strength when receiving this frame, either in dBm, in dB or
>> * unspecified depending on the hardware capabilities flags
>> * @IEEE80211_HW_SIGNAL_*
>> + * @chains: bitmask of receive chains for which separate signal strength
>> + * values were filled.
>> + * @chain_signal: per-chain signal strength, same format as @signal
>
> Oops, sorry, I should've looked at this patch before ... This isn't
> right, @signal can be in "dB" or "unspec" units, but @chain_signal is
> required to be dBm. If you want, I'll edit the patch to just say that it
> must only be provided in dBm?
OK, sounds good.
- Felix
prev parent reply other threads:[~2013-04-22 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 14:29 [PATCH v2 1/2] cfg80211: add support for per-chain signal strength reporting Felix Fietkau
2013-04-22 14:29 ` [PATCH v2 2/2] mac80211: " Felix Fietkau
2013-04-22 14:37 ` Johannes Berg
2013-04-22 14:53 ` Felix Fietkau [this message]
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=51754ED0.5080106@openwrt.org \
--to=nbd@openwrt.org \
--cc=johannes@sipsolutions.net \
--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).