* Fwd: Bluetooth: btusb: Additional Realtek 8822CE Bluetooth device
[not found] <CAD-V9V03cvgp_1W_vjV5GeAyXp+KxaG-8so++8bvSf-zyL07bA@mail.gmail.com>
@ 2019-12-25 13:03 ` Caio Vinicius Santesso
2019-12-26 20:37 ` Marcel Holtmann
0 siblings, 1 reply; 2+ messages in thread
From: Caio Vinicius Santesso @ 2019-12-25 13:03 UTC (permalink / raw)
To: marcel; +Cc: linux-bluetooth
The ASUS TUF Gaming FX505DV_FX505DV laptop contains a Realtek RTL8822CE device.
lsusb output with relevant ID.
Bus 003 Device 002: ID 13d3:3548 IMC Networks Bluetooth Radio
The /sys/kernel/debug/usb/devices portion for this device is:
T: Bus=03 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=13d3 ProdID=3548 Rev= 0.00
S: Manufacturer=Realtek
S: Product=Bluetooth Radio
S: SerialNumber=00e04c000001
C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
The device was able to scan just some of the Bluetooth devices in
pairing mode while using Linux kernel 5.4.0-9-generic. Dualshock 4
wasn't being identified for instance.
So, I've added the following line (#389) inside the blacklist_table[]
block to linux-5.4.6/drivers/bluetooth/btusb.c
{ USB_DEVICE(0x13d3, 0x3548), .driver_info = BTUSB_REALTEK },
built it, and copied to the following directory
make -C /lib/modules/5.4.0-9-generic/build M=$PWD modules
sudo cp btusb.ko /lib/modules/5.4.0-9-generic/kernel/drivers/bluetooth/
loaded and reloaded the relevant module.
sudo modprobe -r btusb
sudo modprobe btusb
Now it is working properly.
$ bluetoothctl devices
Device A4:53:85:F5:04:7C Wireless Controller
Caio V. S. Santesso
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Bluetooth: btusb: Additional Realtek 8822CE Bluetooth device
2019-12-25 13:03 ` Fwd: Bluetooth: btusb: Additional Realtek 8822CE Bluetooth device Caio Vinicius Santesso
@ 2019-12-26 20:37 ` Marcel Holtmann
0 siblings, 0 replies; 2+ messages in thread
From: Marcel Holtmann @ 2019-12-26 20:37 UTC (permalink / raw)
To: Caio Vinicius Santesso; +Cc: linux-bluetooth
Hi Caio,
> The ASUS TUF Gaming FX505DV_FX505DV laptop contains a Realtek RTL8822CE device.
>
> lsusb output with relevant ID.
> Bus 003 Device 002: ID 13d3:3548 IMC Networks Bluetooth Radio
>
> The /sys/kernel/debug/usb/devices portion for this device is:
>
> T: Bus=03 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#= 2 Spd=12 MxCh= 0
> D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=13d3 ProdID=3548 Rev= 0.00
> S: Manufacturer=Realtek
> S: Product=Bluetooth Radio
> S: SerialNumber=00e04c000001
> C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA
> I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
> E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
>
> The device was able to scan just some of the Bluetooth devices in
> pairing mode while using Linux kernel 5.4.0-9-generic. Dualshock 4
> wasn't being identified for instance.
>
> So, I've added the following line (#389) inside the blacklist_table[]
> block to linux-5.4.6/drivers/bluetooth/btusb.c
> { USB_DEVICE(0x13d3, 0x3548), .driver_info = BTUSB_REALTEK },
>
> built it, and copied to the following directory
> make -C /lib/modules/5.4.0-9-generic/build M=$PWD modules
> sudo cp btusb.ko /lib/modules/5.4.0-9-generic/kernel/drivers/bluetooth/
>
> loaded and reloaded the relevant module.
> sudo modprobe -r btusb
> sudo modprobe btusb
>
>
> Now it is working properly.
> $ bluetoothctl devices
> Device A4:53:85:F5:04:7C Wireless Controller
please send a proper patch adding this USB ID to the table.
Regards
Marcel
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-12-26 20:37 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <CAD-V9V03cvgp_1W_vjV5GeAyXp+KxaG-8so++8bvSf-zyL07bA@mail.gmail.com>
2019-12-25 13:03 ` Fwd: Bluetooth: btusb: Additional Realtek 8822CE Bluetooth device Caio Vinicius Santesso
2019-12-26 20:37 ` Marcel Holtmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).