diff options
| author | Jonathan Bakker <xc-racer2@live.ca> | 2018-12-19 12:22:28 +0100 |
|---|---|---|
| committer | Marcel Holtmann <marcel@holtmann.org> | 2018-12-19 13:43:42 +0100 |
| commit | 22bba80500fdf624a7cfbb65fdfa97a038ae224d (patch) | |
| tree | aeab02acbd3420901fe34e0d5c1d745c76c63f6d /net/bluetooth/hci_event.c | |
| parent | e3ca60d06cf37ea57d77eb834dca418f9c2dea81 (diff) | |
| download | linux-stable-22bba80500fdf624a7cfbb65fdfa97a038ae224d.tar.gz linux-stable-22bba80500fdf624a7cfbb65fdfa97a038ae224d.tar.bz2 linux-stable-22bba80500fdf624a7cfbb65fdfa97a038ae224d.zip | |
Bluetooth: hci_bcm: Handle specific unknown packets after firmware loading
The Broadcom controller on aries S5PV210 boards sends out a couple of
unknown packets after the firmware is loaded. This will cause
logging of errors such as:
Bluetooth: hci0: Frame reassembly failed (-84)
This is probably also the case with other boards, as there are related
Android userspace patches for custom ROMs such as
https://review.lineageos.org/#/c/LineageOS/android_system_bt/+/142721/
Since this appears to be intended behaviour, treated them as diagnostic
packets.
Note that this is another variant of commit 01d5e44ace8a
("Bluetooth: hci_bcm: Handle empty packet after firmware loading")
Signed-off-by: Jonathan Bakker <xc-racer2@live.ca>
Signed-off-by: Paweł Chmiel <pawel.mikolaj.chmiel@gmail.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'net/bluetooth/hci_event.c')
0 files changed, 0 insertions, 0 deletions