Bluetooth: hci_qca: Add device_may_wakeup support
authorVenkata Lakshmi Narayana Gubba <gubbaven@codeaurora.org>
Thu, 11 Mar 2021 07:03:40 +0000 (12:33 +0530)
committerMarcel Holtmann <marcel@holtmann.org>
Thu, 11 Mar 2021 10:48:49 +0000 (11:48 +0100)
Based on device may wakeup status, Bluez stack will enable/disable
passive scanning with whitelist in BT controller while suspending.
As interrupt from BT SoC is handled by UART driver,we need to use
device handle of UART driver to get the status of device may wakeup

Signed-off-by: Venkata Lakshmi Narayana Gubba <gubbaven@codeaurora.org>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
drivers/bluetooth/hci_qca.c

index de36af63e1825d1c78ca9e3033e7195d6b57e671..73af901c2032b13021b48ee06fa879f6e7518ae1 100644 (file)
@@ -1571,6 +1571,20 @@ static void qca_cmd_timeout(struct hci_dev *hdev)
        mutex_unlock(&qca->hci_memdump_lock);
 }
 
+static bool qca_prevent_wake(struct hci_dev *hdev)
+{
+       struct hci_uart *hu = hci_get_drvdata(hdev);
+       bool wakeup;
+
+       /* UART driver handles the interrupt from BT SoC.So we need to use
+        * device handle of UART driver to get the status of device may wakeup.
+        */
+       wakeup = device_may_wakeup(hu->serdev->ctrl->dev.parent);
+       bt_dev_dbg(hu->hdev, "wakeup status : %d", wakeup);
+
+       return !wakeup;
+}
+
 static int qca_wcn3990_init(struct hci_uart *hu)
 {
        struct qca_serdev *qcadev;
@@ -1721,6 +1735,7 @@ retry:
                qca_debugfs_init(hdev);
                hu->hdev->hw_error = qca_hw_error;
                hu->hdev->cmd_timeout = qca_cmd_timeout;
+               hu->hdev->prevent_wake = qca_prevent_wake;
        } else if (ret == -ENOENT) {
                /* No patch/nvm-config found, run with original fw/config */
                set_bit(QCA_ROM_FW, &qca->flags);