From: Johannes Berg <johannes@sipsolutions.net>
To: Ashok Raj Nagarajan <arnagara@codeaurora.org>,
Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org,
Ashok Raj Nagarajan <arnagara@qti.qualcomm.com>,
ath10k@lists.infradead.org
Subject: Re: [PATCH 1/2] cfg80211: Add support to set tx power for a station associated
Date: Tue, 15 Nov 2016 10:31:28 +0100 [thread overview]
Message-ID: <1479202288.12007.25.camel@sipsolutions.net> (raw)
In-Reply-To: <8908f6e7bb8ca043fbeb07ee8b004e8f@codeaurora.org>
> In the case of manual intervention by user, the firmware will check
> three
> values - regulatory domain, automatic tx power and user entered
> value.
> System
> will always cap to the minimum of these values and see to that we do
> not
> exceed
> the regulatory power limits.
Fair enough.
> If there are no more comments I will resent this patch series after
> rebase.
I suspect we should also have some kind of capability for all of this,
so it can be used reliably?
johannes
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Ashok Raj Nagarajan <arnagara@codeaurora.org>,
Ben Greear <greearb@candelatech.com>
Cc: Ashok Raj Nagarajan <arnagara@qti.qualcomm.com>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 1/2] cfg80211: Add support to set tx power for a station associated
Date: Tue, 15 Nov 2016 10:31:28 +0100 [thread overview]
Message-ID: <1479202288.12007.25.camel@sipsolutions.net> (raw)
In-Reply-To: <8908f6e7bb8ca043fbeb07ee8b004e8f@codeaurora.org>
> In the case of manual intervention by user, the firmware will check
> three
> values - regulatory domain, automatic tx power and user entered
> value.
> System
> will always cap to the minimum of these values and see to that we do
> not
> exceed
> the regulatory power limits.
Fair enough.
> If there are no more comments I will resent this patch series after
> rebase.
I suspect we should also have some kind of capability for all of this,
so it can be used reliably?
johannes
next prev parent reply other threads:[~2016-11-15 9:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 17:44 [PATCH 1/2] cfg80211: Add support to set tx power for a station associated Ashok Raj Nagarajan
2016-06-14 17:44 ` Ashok Raj Nagarajan
2016-06-28 10:48 ` Johannes Berg
2016-06-28 10:48 ` Johannes Berg
2016-07-05 12:31 ` Ashok Raj Nagarajan
2016-07-05 12:31 ` Ashok Raj Nagarajan
2016-08-01 9:29 ` Johannes Berg
2016-08-01 9:29 ` Johannes Berg
2016-08-01 13:27 ` Ben Greear
2016-08-01 13:27 ` Ben Greear
2016-11-07 14:10 ` Ashok Raj Nagarajan
2016-11-07 14:10 ` Ashok Raj Nagarajan
2016-11-07 14:18 ` Ben Greear
2016-11-07 14:18 ` Ben Greear
2016-11-15 9:31 ` Johannes Berg [this message]
2016-11-15 9:31 ` Johannes Berg
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=1479202288.12007.25.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arnagara@codeaurora.org \
--cc=arnagara@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--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.