[DRAFT] wifi: mt76: mt7925: MT7927 txpower and scan retry fixes#1089
Draft
Komzpa wants to merge 2 commits into
Draft
[DRAFT] wifi: mt76: mt7925: MT7927 txpower and scan retry fixes#1089Komzpa wants to merge 2 commits into
Komzpa wants to merge 2 commits into
Conversation
mt76_get_txpower() reports phy->txpower_cur. mt7925 updates firmware rate power limits, but txpower_cur can remain unset before a later BSS txpower change. That makes userspace observe 0 dBm even when the device has a valid configured/channel power limit. Track whether mac80211 has provided BSS txpower and use it once available. Before that, derive txpower_cur from the configured hw power level, falling back to the current channel max power when the configured level is unset. This keeps TX power reporting grounded before association/BSS setup without changing the scan path. Assisted-by: OpenAI-Codex:gpt-5
On MT7927/MT6639 the firmware can report a successful scan-done event with complete_channel_num == 0 while Bluetooth BR/EDR Inquiry is active. The host scan path then completes normally and userspace observes a successful 2.4 GHz scan with no BSS entries, even though the same networks are visible before and after the Inquiry window. Keep the mac80211 scan pending for this MT7927 case and retry the firmware scan a small number of times after a delay. Limit the workaround to scan requests that include 2.4 GHz channels, since the observed failure is tied to Bluetooth Inquiry coexistence on the 2.4 GHz path. If the retry can be submitted, the original scan completes from the later scan-done event. If retry submission fails or the retry budget is exhausted, complete the scan through the normal path instead of looping indefinitely. Cancel, suspend, and unregister paths abort or cancel the saved scan state so a delayed retry cannot outlive the mac80211 scan and device it belongs to. Assisted-by: OpenAI-Codex:gpt-5
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft only / not for merge yet. This branch mirrors the MT7927 packet for maintainer-visible GitHub review before any canonical linux-wireless submission.
DCO state: these commits intentionally do not carry Signed-off-by yet. Darafei must review and certify DCO before this can become a ready-for-merge PR or an email submission.
Attribution: draft commits carry Assisted-by: OpenAI-Codex:gpt-5.
Scope in this standalone mt76 branch:
Local live evidence from the DKMS build installed on nucat:
Checks on this GitHub branch:
Open question for the scan retry: maintainer feedback is requested on whether host-side delayed retry is acceptable, or whether this should become a firmware/coexistence-state fix instead.
Canonical submission note: Linux wireless still normally wants the DCO-reviewed email series routed through the mt76/wireless maintainers and lists; this draft PR is a staging artifact, not a substitute for that.