Jaguar1 enables EDCCA at bring-up where the vendor driver ships it off
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c, linux
- Domain
- networking
Research direction
Start by reading RtlJaguarDevice::apply_cca and the BB initialization table entry for 0x8a4; the issue also points to tests/dis_cca_tx_onair.sh for related measurements. The issue presents three possible policy changes but leaves the choice unresolved, with regulatory tradeoffs and limited device testing. Done would require settling that policy and implementing and validating the chosen behavior across relevant hardware.
Written by the indexing model from the issue text.
Description
RtlJaguarDevice::apply_cca programs the BB EDCCA thresholds at 0x8a4 from
the live IGI whenever the EDCCA gate is enabled — which is the default — and
0x8a4 is otherwise parked by the BB init table at 0x7f7f, the
never-trigger value. So on Jaguar1 the enable is the active step: bring-up
takes a chip whose BB would never raise EDCCA and gives it a real operating
point.
That is a policy choice worth stating explicitly, because the Realtek vendor
driver makes the opposite one:
CONFIG_RTW_ADAPTIVITY_EN 0— adaptivity (EDCCA) off by default.rtw_adaptivity_en,rtw_adaptivity_mode,rtw_adaptivity_th_l2h_iniand
rtw_adaptivity_th_edcca_hl_diffare all module parameters, mode0644.
devourer enables it and hard-codes both th_l2h_ini (−17, −14 on 8814A) and
the H2L offset (−7).
What this costs, measured on an RTL8812AU injecting 300 frames at 6M on an
idle channel, with two independent witnesses of different families decoding
(RTL8822C and RTL8733BU, agreeing per arm within ~2%):
| arm | delivered |
|---|---|
| both gates on (the default) | 5.7% / 15.7% |
| EDCCA off only | 95.3% / 95.7% |
| primary CCA off only | 31.0% / 12.7% |
| both gates off | 94.0% / 95.0% |
The default costs this family ~90% of what it is asked to transmit, and it is
EDCCA that does it — tests/dis_cca_tx_onair.sh reaches the opposite
conclusion on Jaguar3, where the 8812AU is only ever the flooder.
This is not an argument for dis_cca. With EDCCA off and primary CCA left on,
the same injector delivers 95% on an idle channel and still 78% under a
co-channel flooder — it defers when it should. With both gates off it collapses
to 0.3%, because it stops waiting for a gap and collides instead. The gate
worth turning off is the one the vendor never turned on.
Three things that might follow, in increasing order of change:
- Expose
th_l2h_iniand the H2L offset as tuning config, matching the
vendor's module parameters. Smallest change; makes the operating point a
decision rather than a constant. - Make the Jaguar1 EDCCA enable itself configurable, defaulting to the
current behaviour so nothing moves unless asked. - Follow the vendor and default it off on Jaguar1, on the grounds that the
parked0x7f7fis what the BB table ships and what every other driver
leaves in place.
Raising rather than proposing: a default change has a blast radius I cannot
measure from one bench, and 5 GHz regulatory adaptivity requirements are a
real reason a project might want it on even at this cost. Filed out of
#427, which only split the gate so the two could be told apart.
Verified on RTL8812AU (Jaguar1) and RTL8822C (Jaguar3). Not re-run on
8822EU/8812EU — I do not have those parts.
- Dominant language
- C
- Stars
- 56
- Forks
- 29
- Avg merge
- 3h 43m
- Merged PRs (30d)
- 75
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from OpenIPC/devourer
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Follow-ups left open by the 8822B fast bandwidth toggle fix (#584)Possibly taken @josephnef claimed this today. Openenhancement
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
OpenIPC/devourer#579 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
All issues in OpenIPC/devourer
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
389ds/389-ds-base#8157 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
coolsnowwolf/lede#14305 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days