linux-toradex.git/include/net/bluetooth/bluetooth.h, branch v5.16

Bluetooth: Fix passing NULL to PTR_ERR

2021-09-21T08:44:52+00:00

Passing NULL to PTR_ERR will result in 0 (success), also since the likes of
bt_skb_sendmsg does never return NULL it is safe to replace the instances of
IS_ERR_OR_NULL with IS_ERR when checking its return.

Reported-by: Dan Carpenter 
Tested-by: Tedd Ho-Jeong An 
Signed-off-by: Luiz Augusto von Dentz 
Signed-off-by: Marcel Holtmann

Bluetooth: Add bt_skb_sendmmsg helper

2021-09-13T19:53:23+00:00

This works similarly to bt_skb_sendmsg but can split the msg into
multiple skb fragments which is useful for stream sockets.

Signed-off-by: Luiz Augusto von Dentz 
Signed-off-by: Marcel Holtmann

Bluetooth: Add bt_skb_sendmsg helper

2021-09-13T19:53:22+00:00

bt_skb_sendmsg helps takes care of allocation the skb and copying the
the contents of msg over to the skb while checking for possible errors
so it should be safe to call it without holding lock_sock.

Signed-off-by: Luiz Augusto von Dentz 
Signed-off-by: Marcel Holtmann

Bluetooth: Add support for msbc coding format

2021-09-07T21:09:18+00:00

In Enhanced_Setup_Synchronous_Command, add support for msbc
coding format

Signed-off-by: Kiran K 
Reviewed-by: Chethan T N 
Reviewed-by: Srivatsa Ravishankar 
Signed-off-by: Luiz Augusto von Dentz

Bluetooth: Add support for HCI_Enhanced_Setup_Synchronous_Connection command

2021-09-07T21:09:18+00:00

< HCI Command: Enhanced Setup Synchronous Connection (0x01|0x003d) plen 59
        Handle: 256
        Transmit bandwidth: 8000
        Receive bandwidth: 8000
        Max latency: 13
        Packet type: 0x0380
          3-EV3 may not be used
          2-EV5 may not be used
          3-EV5 may not be used
        Retransmission effort: Optimize for link quality (0x02)
> HCI Event: Command Status (0x0f) plen 4
      Enhanced Setup Synchronous Connection (0x01|0x003d) ncmd 1
        Status: Success (0x00)
> HCI Event: Synchronous Connect Complete (0x2c) plen 17
        Status: Success (0x00)
        Handle: 257
        Address: CC:98:8B:92:04:FD (SONY Visual Products Inc.)
        Link type: eSCO (0x02)
        Transmission interval: 0x0c
        Retransmission window: 0x06
        RX packet length: 60
        TX packet length: 60
        Air mode: Transparent (0x03)

Signed-off-by: Kiran K 
Reviewed-by: Chethan T N 
Reviewed-by: Srivatsa Ravishankar 
Signed-off-by: Luiz Augusto von Dentz

Bluetooth: Allow setting of codec for HFP offload use case

2021-09-07T21:09:18+00:00

This patch allows user space to set the codec that needs to
be used for HFP offload use case. The codec details are cached and
the controller is configured before opening the SCO connection.

Signed-off-by: Kiran K 
Reviewed-by: Chethan T N 
Reviewed-by: Srivatsa Ravishankar 
Signed-off-by: Luiz Augusto von Dentz

Bluetooth: Allow querying of supported offload codecs over SCO socket

2021-09-07T21:09:18+00:00

Add BT_CODEC option for getsockopt systemcall to get the details
of offload codecs supported over SCO socket

Signed-off-by: Kiran K 
Reviewed-by: Chethan T N 
Reviewed-by: Srivatsa Ravishankar 
Signed-off-by: Luiz Augusto von Dentz

Bluetooth: btusb: Fix and detect most of the Chinese Bluetooth controllers

2020-07-28T07:09:00+00:00

For some reason they tend to squat on the very first CSR/
Cambridge Silicon Radio VID/PID instead of paying fees.

This is an extremely common problem; the issue goes as back as 2013
and these devices are only getting more popular, even rebranded by
reputable vendors and sold by retailers everywhere.

So, at this point in time there are hundreds of modern dongles reusing
the ID of what originally was an early Bluetooth 1.1 controller.

Linux is the only place where they don't work due to spotty checks
in our detection code. It only covered a minimum subset.

So what's the big idea? Take advantage of the fact that all CSR
chips report the same internal version as both the LMP sub-version and
HCI revision number. It always matches, couple that with the manufacturer
code, that rarely lies, and we now have a good idea of who is who.

Additionally, by compiling a list of user-reported HCI/lsusb dumps, and
searching around for legit CSR dongles in similar product ranges we can
find what CSR BlueCore firmware supported which Bluetooth versions.

That way we can narrow down ranges of fakes for each of them.

e.g. Real CSR dongles with LMP subversion 0x73 are old enough that
     support BT 1.1 only; so it's a dead giveaway when some
     third-party BT 4.0 dongle reuses it.

So, to sum things up; there are multiple classes of fake controllers
reusing the same 0A12:0001 VID/PID. This has been broken for a while.

Known 'fake' bcdDevices: 0x0100, 0x0134, 0x1915, 0x2520, 0x7558, 0x8891
  IC markings on 0x7558: FR3191AHAL 749H15143 (???)

https://bugzilla.kernel.org/show_bug.cgi?id=60824

Fixes: 81cac64ba258ae (Deal with USB devices that are faking CSR vendor)
Reported-by: Michał Wiśniewski 
Tested-by: Mike Johnson 
Tested-by: Ricardo Rodrigues 
Tested-by: M.Hanny Sabbagh 
Tested-by: Oussama BEN BRAHIM 
Tested-by: Ismael Ferreras Morezuelas 
Signed-off-by: Ismael Ferreras Morezuelas 
Signed-off-by: Marcel Holtmann

Bluetooth: Add support for BT_PKT_STATUS CMSG data for SCO connections

2020-06-12T13:08:49+00:00

This change adds support for reporting the BT_PKT_STATUS to the socket
CMSG data to allow the implementation of a packet loss correction on
erroneous data received on the SCO socket.

The patch was partially developed by Marcel Holtmann and validated by
Hsin-yu Chao.

Signed-off-by: Alain Michaud 
Signed-off-by: Marcel Holtmann

Bluetooth: Introduce debug feature when dynamic debug is disabled

2020-05-11T10:16:27+00:00

In case dynamic debug is disabled, this feature allows a vendor platform
to provide debug statement printing.

Signed-off-by: Marcel Holtmann 
Signed-off-by: Johan Hedberg