From: Valera Kozlov <valera.kozlov19@gmail.com>
To: bmork@telenor.net
Cc: amadeus@jmu.edu.cn, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-wireless@vger.kernel.org, lorenzo@kernel.org, nbd@nbd.name,
ryder.lee@mediatek.com, sean.wang@mediatek.com,
shayne.chen@mediatek.com
Subject: Re: [PATCH 1/1] wifi: mt76: mt7996: fix mixed FEM check of mt7996 chipset
Date: Fri, 21 Aug 2026 11:18:30 +0300 [thread overview]
Message-ID: <20260821081830.280417-1-valera.kozlov19@gmail.com> (raw)
In-Reply-To: <87a4z9f7a5.fsf@miraculix.mork.no>
Device: ASUS ZenWiFi BT8 (RT-BE14000), MediaTek MT7988D SoC (tri-band,
dual PCIe hif/hif2). Confirmed empirically via extended TX PER testing
that adie_idx=1 is correct for this board (matches Chukun's patch),
consistent with a mixed-FEM design.
Readouts from the ADIE_ID registers:
root@bt8:~# echo 0x0f00002c >/sys/kernel/debug/ieee80211/phy0/mt76/regidx
root@bt8:~# grep . /sys/kernel/debug/ieee80211/phy0/mt76/rf_regval
0x79768a20
root@bt8:~# echo 0x1f00002c >/sys/kernel/debug/ieee80211/phy0/mt76/regidx
root@bt8:~# grep . /sys/kernel/debug/ieee80211/phy0/mt76/rf_regval
0x79778a10
root@bt8:~# echo 0x2f00002c >/sys/kernel/debug/ieee80211/phy0/mt76/regidx
root@bt8:~# grep . /sys/kernel/debug/ieee80211/phy0/mt76/rf_regval
0x79778a10
Note that band1/band2 (0x79778a10) match the EE4600 signature exactly
(needs adie_idx=1), but band0 (0x79768a20) differs from both Zyxel
devices reported so far (both show 0x79758a02 regardless of which
adie_idx they need). This is a third, distinct band0 signature -
suggests band0 alone may not reliably disambiguate the two cases,
since devices needing different adie_idx values can share it.
Happy to test further register dumps or a proposed fix on this
hardware if useful.
prev parent reply other threads:[~2026-08-21 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 12:01 [PATCH 1/1] wifi: mt76: mt7996: fix mixed FEM check of mt7996 chipset Chukun Pan
2025-12-19 16:23 ` Bjørn Mork
2025-12-23 14:00 ` Chukun Pan
2025-12-23 17:16 ` Bjørn Mork
2026-08-21 8:18 ` Valera Kozlov [this message]
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=20260821081830.280417-1-valera.kozlov19@gmail.com \
--to=valera.kozlov19@gmail.com \
--cc=amadeus@jmu.edu.cn \
--cc=bmork@telenor.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@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