From: Josef Schlehofer <pepe.schlehofer@gmail.com>
To: Sean Wang <sean.wang@mediatek.com>,
JB Tsai <jb.tsai@mediatek.com>,
Allan Wang <allan.wang@mediatek.com>
Cc: Felix Fietkau <nbd@nbd.name>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Ryder Lee <ryder.lee@mediatek.com>,
Shayne Chen <shayne.chen@mediatek.com>,
Quan Zhou <quan.zhou@mediatek.com>,
linux-wireless@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: mt7925: status LED of USB adapters and linux-firmware
Date: Mon, 12 Oct 2026 14:53:10 +0200 [thread overview]
Message-ID: <20261012125310.13917-1-pepe.schlehofer@gmail.com> (raw)
Hi,
The status LED of MT7925 USB adapters stays off on Linux. I
investigated this with a NETGEAR A9000 (0846:9072), see [1].
MediaTek's Windows driver for the A9000 (mtkwecxu.sys 5.3.0.3230)
controls the LED using UNI command 0x2a, with GPIO 8 and a TLV (tag 1)
specifying the LED state (on/off). Sending the same command from mt76
works with the firmware from the Windows driver package
(MT7925_E1_ASIC_ROM_RAM_CE_2249_CCN10_USB, 20250424), but not with
linux-firmware builds (CE_2249_CCN16, tested with 20231227 and
20260813). The latter return status 0 but do not change the LED state.
All 16 MT7925 firmware releases currently in linux-firmware are CCN16
builds.
Could you clarify:
1. Can GPIO-based LED control be enabled in the linux-firmware build
for MT7925 USB adapters?
2. If not, what is the intended way to control these LEDs on Linux?
3. Is GPIO 8 common to all MT7925 USB adapters, or is it
board-specific?
I have a small mt76 patch that registers the LED for MT7925 USB devices
and sends this command. I will submit it once firmware support and GPIO
selection are clarified.
[1] https://github.com/morrownr/USB-WiFi/issues/731
Thanks,
Josef
reply other threads:[~2026-10-12 12:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261012125310.13917-1-pepe.schlehofer@gmail.com \
--to=pepe.schlehofer@gmail.com \
--cc=allan.wang@mediatek.com \
--cc=jb.tsai@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--cc=quan.zhou@mediatek.com \
--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