linux-stable.git/drivers/bluetooth/btintel.c, branch v6.15

Bluetooth: btintel: Add support to configure TX power

2025-03-25T16:51:42+00:00

BRDS - Bluetooth Regulatory Domain Specific absorption rate

Bluetooth has regulatory limitations which prohibit or allow usage of certain
bands or channels as well as limiting Tx power. The Tx power values can be
configured in ACPI table. This patch reads from ACPI entry configures the
controller accordingly.

Signed-off-by: Kiran K 
Signed-off-by: Vijay Satija 
Signed-off-by: Luiz Augusto von Dentz

Bluetooth: btintel: Add DSBR support for ScP

2025-03-25T16:31:41+00:00

Add DSBR support for Scorpious Peak cores.

Refer commit eb9e749c0182 ("Bluetooth: btintel: Allow configuring drive
strength of BRI") for details about DSBR.

Signed-off-by: Kiran K 
Signed-off-by: Luiz Augusto von Dentz

Bluetooth: btintel: Add support for Intel Scorpius Peak

2025-03-25T16:29:51+00:00

Add support for Scorpious Peak core.

Signed-off-by: Kiran K 
Signed-off-by: Luiz Augusto von Dentz

Bluetooth: Use str_enable_disable-like helpers

2025-01-15T15:36:11+00:00

Replace ternary (condition ? "enable" : "disable") syntax with helpers
from string_choices.h because:
1. Simple function call with one argument is easier to read.  Ternary
   operator has three arguments and with wrapping might lead to quite
   long code.
2. Is slightly shorter thus also easier to read.
3. It brings uniformity in the text - same string.
4. Allows deduping by the linker, which results in a smaller binary
   file.

Signed-off-by: Krzysztof Kozlowski 
Signed-off-by: Luiz Augusto von Dentz

Bluetooth: btintel: Direct exception event to bluetooth stack

2024-11-14T20:40:55+00:00

Have exception event part of HCI traces which helps for debug.

snoop traces:
> HCI Event: Vendor (0xff) plen 79
        Vendor Prefix (0x8780)
      Intel Extended Telemetry (0x03)
        Unknown extended telemetry event type (0xde)
        01 01 de
        Unknown extended subevent 0x07
        01 01 de 07 01 de 06 1c ef be ad de ef be ad de
        ef be ad de ef be ad de ef be ad de ef be ad de
        ef be ad de 05 14 ef be ad de ef be ad de ef be
        ad de ef be ad de ef be ad de 43 10 ef be ad de
        ef be ad de ef be ad de ef be ad de

Fixes: af395330abed ("Bluetooth: btintel: Add Intel devcoredump support")
Signed-off-by: Kiran K 
Signed-off-by: Luiz Augusto von Dentz

Bluetooth: btintel: Do no pass vendor events to stack

2024-11-14T20:32:28+00:00

During firmware download, vendor specific events like boot up and
secure send result are generated. These events can be safely processed at
the driver level. Passing on these events to stack prints unnecessary
log as below.

    Bluetooth: hci0: Malformed MSFT vendor event: 0x02

Fixes: 3368aa357f3b ("Bluetooth: msft: Handle MSFT Monitor Device Event")
Signed-off-by: Kiran K 
Signed-off-by: Luiz Augusto von Dentz

Bluetooth: btintel: Add DSBR support for BlazarIW, BlazarU and GaP

2024-11-14T20:31:30+00:00

Add DSBR support for BlazarIW, BlazarU and Gale Peak2 cores.

Refer commit eb9e749c0182 ("Bluetooth: btintel: Allow configuring drive
strength of BRI") for details about DSBR.

Signed-off-by: Kiran K 
Signed-off-by: Luiz Augusto von Dentz

Bluetooth: btintel_pcie: Add recovery mechanism

2024-11-14T20:30:53+00:00

This patch adds a recovery mechanism to recover controller if firmware
download fails due to unresponsive controller, command timeout, firmware
signature verification failure etc. Driver attmepts maximum of 5 times
before giving up.

Signed-off-by: Kiran K 
Signed-off-by: Luiz Augusto von Dentz

Bluetooth: btintel_pcie: Add handshake between driver and firmware

2024-11-14T20:30:34+00:00

The following handshake mechanism needs be followed after firmware
download is completed to bring the firmware to running state.

After firmware fragments of Operational image are downloaded and
secure sends result of the image succeeds,

1. Driver sends HCI Intel reset with boot option #1 to switch FW image.
2. FW sends Alive GP[0] MSIx
3. Driver enables data path (doorbell 0x460 for RBDs, etc...)
4. Driver gets Bootup event from firmware
5. Driver performs D0 entry to device (WRITE to IPC_Sleep_Control =0x0)
6. FW sends Alive GP[0] MSIx
7. Device host interface is fully set for BT protocol stack operation.
8. Driver may optionally get debug event with ID 0x97 which can be dropped

For Intermediate loadger image, all the above steps are applicable
expcept #5 and #6.

On HCI_OP_RESET, firmware raises alive interrupt. Driver needs to wait
for it before passing control over to bluetooth stack.

Co-developed-by: Devegowda Chandrashekar 
Signed-off-by: Devegowda Chandrashekar 
Signed-off-by: Kiran K 
Signed-off-by: Luiz Augusto von Dentz

bluetooth: Fix typos in the comments

2024-11-14T20:28:07+00:00

Correctly spelled comments make it easier for the reader to understand
the code.

Fix typos:
'fragement' ==> 'fragment',
'genration' ==> 'generation',
'funciton' ==> 'function',
'Explitly' ==> 'Explicitly',
'explaination' ==> 'explanation',
'Tranlate' ==> 'Translate',
'immediatelly' ==> 'immediately',
'isntance' ==> 'instance',
'transmittion' ==> 'transmission',
'recevie' ==> 'receive',
'outselves' ==> 'ourselves',
'conrol' ==> 'control'.

Signed-off-by: Yan Zhen 
Reviewed-by: AngeloGioacchino Del Regno 
Signed-off-by: Luiz Augusto von Dentz