From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Felix Fietkau <nbd@nbd.name>,
Lucid Duck <lucid_duck@justthetip.ca>,
linux-wireless@vger.kernel.org
Cc: Lorenzo Bianconi <lorenzo@kernel.org>,
Ryder Lee <ryder.lee@mediatek.com>
Subject: Re: [PATCH] wifi: mt76: connac: fix txpower_cur not being updated
Date: Tue, 27 Jan 2026 18:17:36 +0200 [thread overview]
Message-ID: <f677b9d5-235c-4ff4-be36-c71c43b6988a@gmail.com> (raw)
In-Reply-To: <4ddb4417-d623-44ae-878d-5ee5939f2826@nbd.name>
On 27/01/2026 14:21, Felix Fietkau wrote:
> On 25.01.26 23:22, Lucid Duck wrote:
>> The mt76_connac_mcu_set_rate_txpower() function sends TX power settings
>> to the firmware but never updates phy->txpower_cur. This causes
>> mt76_get_txpower() to return stale or incorrect values (typically
>> showing 3 dBm regardless of actual transmit power) when userspace
>> queries TX power via nl80211.
>>
>> This affects MT7921 and other connac-based devices. Users observe:
>> $ iw dev wlan0 info
>> ...
>> txpower 3.00 dBm
>>
>> The firmware receives and applies the correct power level, but the
>> reported value is wrong because txpower_cur is never set.
>>
>> Fix by updating phy->txpower_cur after successfully configuring TX
>> power, matching the behavior of other mt76 drivers like mt7915.
>>
>> Signed-off-by: Lucid Duck <lucid_duck@justthetip.ca>
>> ---
>> drivers/net/wireless/mediatek/mt76/mt76_connac_mcu.c | 8 +++++++-
>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/wireless/mediatek/mt76/mt76_connac_mcu.c b/drivers/net/wireless/mediatek/mt76/mt76_connac_mcu.c
>> index 045771228..7cd357419 100644
>> --- a/drivers/net/wireless/mediatek/mt76/mt76_connac_mcu.c
>> +++ b/drivers/net/wireless/mediatek/mt76/mt76_connac_mcu.c
>> @@ -2251,7 +2251,7 @@ mt76_connac_mcu_rate_txpower_band(struct mt76_phy *phy,
>> int mt76_connac_mcu_set_rate_txpower(struct mt76_phy *phy)
>> {
>> - int err;
>> + int err, tx_power;
>> if (phy->cap.has_2ghz) {
>> err = mt76_connac_mcu_rate_txpower_band(phy,
>> @@ -2272,6 +2272,12 @@ int mt76_connac_mcu_set_rate_txpower(struct mt76_phy *phy)
>> return err;
>> }
>> + /* Update txpower_cur for accurate reporting via nl80211 */
>> + tx_power = 2 * phy->hw->conf.power_level;
>> + if (!tx_power)
>> + tx_power = 127;
>> + phy->txpower_cur = tx_power;
>
> phy->hw->conf.power_level is the user configured power level, not what the hardware is capable of transmitting.
>
> To fix it properly, I think you should determine the maximum rate power used in the loop within mt76_connac_mcu_rate_txpower_band (updated with each call).
>
> - Felix
>
What about these older patches?
https://patchwork.kernel.org/project/linux-wireless/list/?series=932665&submitter=&state=*&q=&archive=&delegate=
next prev parent reply other threads:[~2026-01-27 16:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 22:22 [PATCH] wifi: mt76: connac: fix txpower_cur not being updated Lucid Duck
2026-01-27 1:59 ` Nick
2026-01-27 12:21 ` Felix Fietkau
2026-01-27 16:17 ` Bitterblue Smith [this message]
2026-01-27 17:00 ` Felix Fietkau
2026-01-30 21:54 ` [PATCH v2] wifi: mt76: mt7921: fix txpower reporting Lucid Duck
2026-02-10 3:02 ` Nick
2026-02-12 2:46 ` Lucid Duck
2026-03-09 21:50 ` Lucid Duck
2026-03-12 6:38 ` Sean Wang
2026-03-17 17:30 ` [PATCH v3 0/1] wifi: mt76: mt7921: fix txpower reporting from rate power configuration Lucid Duck
2026-03-17 17:30 ` [PATCH v3 1/1] " Lucid Duck
2026-03-17 21:51 ` Lucid Duck
2026-03-19 6:00 ` Sean Wang
2026-03-19 20:38 ` [PATCH v4] " Lucid Duck
2026-03-20 1:17 ` Lucid Duck
2026-03-20 6:34 ` Greg KH
2026-03-21 8:58 ` Sean Wang
2026-01-30 21:58 ` [PATCH v2] wifi: mt76: mt7921: fix txpower reporting Lucid Duck
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=f677b9d5-235c-4ff4-be36-c71c43b6988a@gmail.com \
--to=rtl8821cerfe2@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=lucid_duck@justthetip.ca \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox