mt7615: 5Ghz sku_txpower limits (in DTS) do not work in DBDC mode.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
Hi there,
I am trying to limit the txpower by our certificated power table with FCC and IC.
Info:
mt76 version: mt76-2021-12-03-678071
OpenWrt version: 21.02.3
Chip: mt7615D (DBDC mode)
Test and result:
So far, I have checked the txpower limitation can work in MTK jedi SDK.
In OpenWrt, I replaced the the WIFI Firmware (cr4, n9, and its patch) by those in MTK jedi SDK.
And make sure req.txpower_sku[], format_id, sku_enable, band_idx, are the same between OpenWrt and jedi SDK.
Moreover, I found that our certificated power table can work if I set the VHT20 txpower limit all at 14dBm.
But I can not find the reason. Hope anyone can help me...
Thanks.
I added the US txpower limit table in DTS and I printed related data as the following snippet:
int mt7615_mcu_set_chan_info(struct mt7615_phy *phy, int cmd)
{
...
// print req.txpower_sku[] //
return mt76_mcu_send_msg(&dev->mt76, cmd, &req, sizeof(req), true);
}
int mt7615_mcu_set_sku_en(struct mt7615_phy *phy, bool enable)
{
...
// print format_id, band_idx , and band_idx //
return mt76_mcu_send_msg(&dev->mt76,
MCU_EXT_CMD_TX_POWER_FEATURE_CTRL, &req,
sizeof(req), true);
}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the DTS power table and the mt7615_mcu_set_chan_info and mt7615_mcu_set_sku_en entry points named in the report. Compare the printed request fields with the MTK Jedi SDK behavior for mt7615D DBDC mode, then verify that the certified 5 GHz limits apply without setting every VHT20 limit to 14 dBm.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100