Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mt76x0: change Tx band power to 1 dBm per step #665

Closed
wants to merge 1 commit into from
Closed

mt76x0: change Tx band power to 1 dBm per step #665

wants to merge 1 commit into from

Conversation

DragonBluep
Copy link

No description provided.

@DragonBluep
Copy link
Author

There is no definition of 1step=0.5 dBm in mt7610 eeprom content. According to the feedback, when 1step = 1 dBm, the correct transmit power can be obtained.
mt7610 band power.pdf

#606 TP-LINK RE200 problem with the operation of the WLAN chipset. OpenWRT rel 21.02rc4
#604 MT7610E: TX-Power Values incorrect -> low range
#577 MT76x0: Correct VHT MCS 8/9 tx power eeprom offset
#530 Low transmission power on MT7610EN
#484 low tx power with mt76x0e driver
#227 Various issues with 5Ghz MT7610E
#216 low tx power m7610e

@namidairo
Copy link
Contributor

There is no definition of 1step=0.5 dBm in mt7610 eeprom content. According to the feedback, when 1step = 1 dBm, the correct transmit power can be obtained.

At the very least, I recall power delta being 0.5db steps. I can't remember if there was a multiply or bit shift after that to normalise it though. However, since that also affects the value, you should probably double check that.

I'm not sure what's going on with 7610, but I think you ought to just log TX_ALC_CFG_0 writes on stock and mt76 just to make sure you don't accidentally do something potentially out of spec/regulations

@DragonBluep
Copy link
Author

Seems I misunderstood so it's time to close it.

@DragonBluep DragonBluep deleted the pr_fix_mt76x0_tx_power branch May 4, 2022 22:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants