diff mbox series

[RFC,v2] Bluetooth: hci_qca: Add device_may_wakeup support

Message ID 1615446220-969-1-git-send-email-gubbaven@codeaurora.org (mailing list archive)
State Accepted
Commit c1a74160eaf1ac218733b371158432b52601beff
Headers show
Series [RFC,v2] Bluetooth: hci_qca: Add device_may_wakeup support | expand

Commit Message

Venkata Lakshmi Narayana Gubba March 11, 2021, 7:03 a.m. UTC
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>
---
 drivers/bluetooth/hci_qca.c | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

Comments

Marcel Holtmann March 11, 2021, 10:49 a.m. UTC | #1
Hi Venkata,

> 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>
> ---
> drivers/bluetooth/hci_qca.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)

patch has been applied to bluetooth-next tree.

Regards

Marcel
patchwork-bot+linux-arm-msm@kernel.org May 26, 2021, 7:03 p.m. UTC | #2
Hello:

This patch was applied to qcom/linux.git (refs/heads/for-next):

On Thu, 11 Mar 2021 12:33:40 +0530 you wrote:
> 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>
> 
> [...]

Here is the summary with links:
  - [RFC,v2] Bluetooth: hci_qca: Add device_may_wakeup support
    https://git.kernel.org/qcom/c/c1a74160eaf1

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
diff mbox series

Patch

diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c
index de36af6..73af901 100644
--- a/drivers/bluetooth/hci_qca.c
+++ b/drivers/bluetooth/hci_qca.c
@@ -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 @@  static int qca_setup(struct hci_uart *hu)
 		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);