[PATCH AUTOSEL 6.19] wifi: rtw89: 8852au: add support for TP TX30U Plus

Sasha Levin
2026-02-14T21:25:55Z

From: Jan Gerber <j@mailb.org>

[ Upstream commit a2f1fc9ab6fb0d5c9d701a516c342944258fb20e ]

the device shows up like this and everything seams to work:

Bus 004 Device 003: ID 3625:010d Realtek 802.11ax WLAN Adapter

Signed-off-by: Jan Gerber <j@mailb.org>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
Link: https://patch.msgid.link/20251212005515.2059533-1-j@mailb.org
Signed-off-by: Sasha Levin <sashal@kernel.org>
---

LLM Generated explanations, may be completely bogus:

## Analysis: wifi: rtw89: 8852au: add support for TP TX30U Plus

### Commit Message Analysis
This commit adds a new USB device ID (`0x3625:0x010d`) for the TP TX30U
Plus WiFi adapter to the existing `rtw8852au` driver. The commit message
indicates the device was tested and works ("everything seams to work").
It was acked by the Realtek subsystem maintainer (Ping-Ke Shih).

### Code Change Analysis
The change is a **two-line addition** of a single USB device ID entry to
an existing device ID table:

```c
{ USB_DEVICE_AND_INTERFACE_INFO(0x3625, 0x010d, 0xff, 0xff, 0xff),
.driver_info = (kernel_ulong_t)&rtw89_8852au_info },
```

This is inserted in sorted order among existing entries. Notably, the
same vendor (`0x3625`) already has another device (`0x010f`) in the
table, so this vendor's devices are already known to work with this
driver.

### Classification: New Device ID Addition

This falls squarely into the **"NEW DEVICE IDs"** exception category for
stable backports:

1. **The driver already exists** in stable trees - `rtw8852au` is an
established driver
2. **Only the ID is new** - no driver code changes whatsoever
3. **Same vendor already supported** - `0x3625:0x010f` is already in the
table, meaning the `0x3625` vendor's devices are known to work
4. **Trivially correct** - it's a mechanical two-line addition following
the exact same pattern as every other entry in the table

### Risk Assessment
- **Risk: Essentially zero.** Adding a USB device ID to a table cannot
break existing functionality. It only enables the existing driver to
bind to a new USB VID:PID combination.
- **Scope: Minimal.** Two lines, one file, one table entry.
- **Dependencies: None.** The driver infrastructure is already in place.

### User Impact
- Users with the TP TX30U Plus WiFi adapter on stable kernels currently
have **no WiFi support** for this device
- With this backport, their device would be recognized and work with the
existing driver
- This is the kind of fix that directly enables hardware for real users

### Stability Indicators
- Acked and signed off by Realtek's kernel maintainer (Ping-Ke Shih)
- Tested by the submitter with real hardware
- Same vendor's other device already works with this driver

### Conclusion
This is a textbook device ID addition - the most common and safest type
of stable backport. It enables real hardware for real users with zero
risk of regression. The change is trivially correct, tested, and
acknowledged by the subsystem maintainer.

**YES**

drivers/net/wireless/realtek/rtw89/rtw8852au.c | 2 ++
1 file changed, 2 insertions(+)

diff --git a/drivers/net/wireless/realtek/rtw89/rtw8852au.c b/drivers/net/wireless/realtek/rtw89/rtw8852au.c
index ca782469c455d..74a976c984ad8 100644
--- a/drivers/net/wireless/realtek/rtw89/rtw8852au.c
+++ b/drivers/net/wireless/realtek/rtw89/rtw8852au.c
@@ -60,6 +60,8 @@ static const struct usb_device_id rtw_8852au_id_table[] = {
.driver_info = (kernel_ulong_t)&rtw89_8852au_info },
{ USB_DEVICE_AND_INTERFACE_INFO(0x2357, 0x0141, 0xff, 0xff, 0xff),
.driver_info = (kernel_ulong_t)&rtw89_8852au_info },
+ { USB_DEVICE_AND_INTERFACE_INFO(0x3625, 0x010d, 0xff, 0xff, 0xff),
+ .driver_info = (kernel_ulong_t)&rtw89_8852au_info },
{ USB_DEVICE_AND_INTERFACE_INFO(0x3625, 0x010f, 0xff, 0xff, 0xff),
.driver_info = (kernel_ulong_t)&rtw89_8852au_info },
{},
--
2.51.0