From: Bob Copeland <me@bobcopeland.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Balaji Pothunoori <bpothuno@codeaurora.org>,
johannes@sipsolutions.net,
Ashok Raj Nagarajan <arnagara@codeaurora.org>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH v4 3/3] ath10k: add support for controlling tx power to a station
Date: Wed, 18 Sep 2019 20:21:00 -0400 [thread overview]
Message-ID: <20190919002100.GA28186@localhost> (raw)
In-Reply-To: <871rwdbu1p.fsf@kamboji.qca.qualcomm.com>
On Wed, Sep 18, 2019 at 04:41:54PM +0300, Kalle Valo wrote:
> Bob Copeland <me@bobcopeland.com> writes:
> > - on A, changed the global tx power limit to 1 dBm
> > -> result: signal level dropped to ~ -95 dBm
> >
> > Reading the description above, now I'm wondering if the txpower is
> > max(sta-power,global-power)? If so, that seems a bit unintuitive to me,
> > or at least isn't what I hoped for. I'd prefer to have per-sta power
> > setting override the global power.
>
> Balaji, please reply to Bob's questions. I missed this thread while
> applying v5, sorry Bob.
Just to follow-up, I ran more experiments since writing the above
email and it didn't look like it was doing max() either -- at least
on my hardware/firmware combo it had no effect at all that I could tell.
I did verify that the wmi update went through to the firmware.
I can't remember now, but I may have been testing mesh mode in case
that makes a difference.
--
Bob Copeland %% https://bobcopeland.com/
next prev parent reply other threads:[~2019-09-19 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 10:49 [PATCH v4 3/3] ath10k: add support for controlling tx power to a station Balaji Pothunoori
2019-04-02 22:37 ` Bob Copeland
2019-09-18 13:41 ` Kalle Valo
2019-09-19 0:21 ` Bob Copeland [this message]
2019-09-19 8:04 ` Balaji Pothunoori
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=20190919002100.GA28186@localhost \
--to=me@bobcopeland.com \
--cc=arnagara@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=bpothuno@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=kvalo@codeaurora.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).