From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christoph Zwerschke <cito@online.de>,
Max Chou <max.chou@realtek.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
linux-bluetooth@vger.kernel.org, regressions@lists.linux.dev,
"ra.prism" <ra.prism@gmail.com>
Subject: Re: [REGRESSION] btusb: ASUS USB-BT540/BT600 IDs backported without, RTL8761CUV support, adapter re-enumerates endlessly (6.18.50, 6.12.109,, 6.1.188, 5.15.221, 5.10.270)
Date: Mon, 14 Sep 2026 22:03:32 -0400 [thread overview]
Message-ID: <daily-reply-0016-re-btusb-rtl8761cuv-regression@kernel.org> (raw)
In-Reply-To: <9ac1c05b-e9f2-49e9-af63-9cd0e42115fc@gmail.com>
> Both set BTUSB_REALTEK for 0b05:1bef / 0b05:1d70, so the adapters now go
> through btrtl setup. btrtl only learned about this chip in v6.19-rc1:
>
> 4a23ce935f74 ("Bluetooth: btrtl: Add the support for RTL8761CUV")
Thanks for the detailed report, this is a good catch.
4a23ce935f74 ("Bluetooth: btrtl: Add the support for RTL8761CUV") is queued
for 6.18 and 6.12, which closes it on those two.
It cannot go to 6.6, 6.1, 5.15 or 5.10: btrtl there has no .hw_info field,
IC_INFO() still takes four arguments, and CHIP_ID_8922A, CHIP_ID_8852BT and
hci_set_quirk() are all absent, so it does not build. Those four trees get
980084de4d9b ("Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU") and
6f0624b4427e ("Bluetooth: btusb: Add ASUS USB-BT600 for Realtek 8761CU")
reverted instead, which puts the adapters back on the generic path they were on
before.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-09-15 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 11:44 [REGRESSION] btusb: ASUS USB-BT540/BT600 IDs backported without, RTL8761CUV support, adapter re-enumerates endlessly (6.18.50, 6.12.109,, 6.1.188, 5.15.221, 5.10.270) ra.prism
2026-09-15 2:03 ` Sasha Levin [this message]
2026-09-20 13:49 ` Christoph Zwerschke
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=daily-reply-0016-re-btusb-rtl8761cuv-regression@kernel.org \
--to=sashal@kernel.org \
--cc=cito@online.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=max.chou@realtek.com \
--cc=ra.prism@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.