Bluetooth: hci_qca: Update baudrate change wait time for wcn3990

This patch will update the baudrate change request wait time from 300 ms to 100 ms. When host sends the change baudrate request to the controller, controller sets its clock and wait until the clocks settle down. Here the Wait time is required for both host and controller to be on sync.

Signed-off-by Balakrishna Godavarthi <[email protected]>

---
 drivers/bluetooth/hci_qca.c | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

drivers/bluetooth/hci_qca.c +0 -0

index 5e03504c4e0c..22f3c983f868 100644

Hi Balakrishna,

Quoted 16 lines · Balakrishna Godavarthi

This patch will update the baudrate change request wait time from 300 ms to 100 ms. When host sends the change baudrate request to the controller, controller sets its clock and wait until the clocks settle down. Here the Wait time is required for both host and controller to be on sync.

Signed-off-by Balakrishna Godavarthi <[email protected]>

---
 drivers/bluetooth/hci_qca.c | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

drivers/bluetooth/hci_qca.c +0 -0

index 5e03504c4e0c..22f3c983f868 100644

drivers/bluetooth/hci_qca.c line 63

Quoted 6 lines

drivers/bluetooth/hci_qca.c +2 -1

@@ -59,7 +59,8 @@
 
 #define IBS_WAKE_RETRANS_TIMEOUT_MS	100
 #define IBS_TX_IDLE_TIMEOUT_MS		2000
-#define BAUDRATE_SETTLE_TIMEOUT_MS	300
+#define ROME_BD_SETTLE_TIMEOUT_MS	300
+#define WCN3990_BD_SETTLE_TIMEOUT_MS	100

nit: _BR_ instead of _BD_?

drivers/bluetooth/hci_qca.c static int qca_set_baudrate(struct hci_dev *hdev, uint8_t baudrate) · line 970

Quoted 9 lines

drivers/bluetooth/hci_qca.c +2 -0

 #define POWER_PULSE_TRANS_TIMEOUT_MS	100
 
 /* susclk rate */

@@ -965,8 +966,11 @@ static int qca_set_baudrate(struct hci_dev *hdev, uint8_t baudrate)
 	struct hci_uart *hu = hci_get_drvdata(hdev);
 	struct qca_data *qca = hu->priv;
 	struct sk_buff *skb;
+	struct qca_serdev *qcadev;
+	unsigned int bd_settling_timeout;

nit: from the context the purpose of the variable is fairly clear, calling it just 'timeout' (or 'settling_time', it's not really a timeout) should be fine.

That said, I have a similar change in my pipeline, which further reduces the time to the 'strictly necessary'. It's slightly more code though. I guess I'll send it and we can discuss/let Marcel decide what to adopt.