linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [kernel PATCH v1] Bluetooth: hci_qca: get wakeup status from serdev device handle
@ 2023-02-02 17:47 Zhengping Jiang
  2023-02-02 21:20 ` patchwork-bot+bluetooth
  0 siblings, 1 reply; 2+ messages in thread
From: Zhengping Jiang @ 2023-02-02 17:47 UTC (permalink / raw)
  To: linux-bluetooth, marcel, luiz.dentz
  Cc: chromeos-bluetooth-upstreaming, Zhengping Jiang, Johan Hedberg,
	Venkata Lakshmi Narayana Gubba, linux-kernel

Bluetooth controller attached via the UART is handled by the serdev driver.
Get the wakeup status from the device handle through serdev, instead of the
parent path.

Fixes: c1a74160eaf1 ("Bluetooth: hci_qca: Add device_may_wakeup support")
Signed-off-by: Zhengping Jiang <jiangzp@google.com>
---

Changes in v1:
- Get wakeup status from device handle of serdev driver

 drivers/bluetooth/hci_qca.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c
index a5c19f32926b..3df8c3606e93 100644
--- a/drivers/bluetooth/hci_qca.c
+++ b/drivers/bluetooth/hci_qca.c
@@ -1588,10 +1588,11 @@ static bool qca_wakeup(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.
+	/* BT SoC attached through the serial bus is handled by the serdev driver.
+	 * So we need to use the device handle of the serdev driver to get the
+	 * status of device may wakeup.
 	 */
-	wakeup = device_may_wakeup(hu->serdev->ctrl->dev.parent);
+	wakeup = device_may_wakeup(&hu->serdev->ctrl->dev);
 	bt_dev_dbg(hu->hdev, "wakeup status : %d", wakeup);
 
 	return wakeup;
-- 
2.39.1.519.gcb327c4b5f-goog


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [kernel PATCH v1] Bluetooth: hci_qca: get wakeup status from serdev device handle
  2023-02-02 17:47 [kernel PATCH v1] Bluetooth: hci_qca: get wakeup status from serdev device handle Zhengping Jiang
@ 2023-02-02 21:20 ` patchwork-bot+bluetooth
  0 siblings, 0 replies; 2+ messages in thread
From: patchwork-bot+bluetooth @ 2023-02-02 21:20 UTC (permalink / raw)
  To: Zhengping Jiang
  Cc: linux-bluetooth, marcel, luiz.dentz,
	chromeos-bluetooth-upstreaming, johan.hedberg, gubbaven,
	linux-kernel

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Thu,  2 Feb 2023 09:47:01 -0800 you wrote:
> Bluetooth controller attached via the UART is handled by the serdev driver.
> Get the wakeup status from the device handle through serdev, instead of the
> parent path.
> 
> Fixes: c1a74160eaf1 ("Bluetooth: hci_qca: Add device_may_wakeup support")
> Signed-off-by: Zhengping Jiang <jiangzp@google.com>
> 
> [...]

Here is the summary with links:
  - [kernel,v1] Bluetooth: hci_qca: get wakeup status from serdev device handle
    https://git.kernel.org/bluetooth/bluetooth-next/c/3d29daf4b155

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



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-02-02 21:20 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-02 17:47 [kernel PATCH v1] Bluetooth: hci_qca: get wakeup status from serdev device handle Zhengping Jiang
2023-02-02 21:20 ` patchwork-bot+bluetooth

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).