From: Chris Lu <chris.lu@mediatek.com>
To: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Von Dentz <luiz.dentz@gmail.com>
Cc: Sean Wang <sean.wang@mediatek.com>,
Deren Wu <deren.Wu@mediatek.com>,
Aaron Hou <aaron.hou@mediatek.com>,
Steve Lee <steve.lee@mediatek.com>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mediatek <linux-mediatek@lists.infradead.org>,
Chris Lu <chris.lu@mediatek.com>
Subject: [PATCH v4 2/4] Bluetooth: btusb: add callback function in btusb suspend/resume
Date: Thu, 6 Jun 2024 19:43:19 +0800 [thread overview]
Message-ID: <20240606114321.30515-3-chris.lu@mediatek.com> (raw)
In-Reply-To: <20240606114321.30515-1-chris.lu@mediatek.com>
Add new function: dev_suspend/dev_resume in btusb_data which are reserved
for vendor specific usage during suspend/resume. dev_suspend will be
added before stop traffic in btusb_suspend and dev_resume will be
added after resubmit urb in btusb_resuem.
Signed-off-by: Chris Lu <chris.lu@mediatek.com>
Signed-off-by: Sean Wang <sean.wang@mediatek.com>
---
drivers/bluetooth/btusb.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 79aefdb3324d..83765c0c14b4 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -891,6 +891,9 @@ struct btusb_data {
int (*setup_on_usb)(struct hci_dev *hdev);
+ int (*dev_suspend)(struct hci_dev *hdev);
+ int (*dev_resume)(struct hci_dev *hdev);
+
int oob_wake_irq; /* irq for out-of-band wake-on-bt */
unsigned cmd_timeout_cnt;
@@ -4715,6 +4718,9 @@ static int btusb_suspend(struct usb_interface *intf, pm_message_t message)
cancel_work_sync(&data->work);
+ if (data->dev_suspend)
+ data->dev_suspend(data->hdev);
+
btusb_stop_traffic(data);
usb_kill_anchored_urbs(&data->tx_anchor);
@@ -4818,6 +4824,9 @@ static int btusb_resume(struct usb_interface *intf)
btusb_submit_isoc_urb(hdev, GFP_NOIO);
}
+ if (data->dev_resume)
+ data->dev_resume(hdev);
+
spin_lock_irq(&data->txlock);
play_deferred(data);
clear_bit(BTUSB_SUSPENDING, &data->flags);
--
2.18.0
next prev parent reply other threads:[~2024-06-06 11:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 11:43 [PATCH v4 0/4] Bluetooth: btusb: MediaTek ISO data transmission Chris Lu
2024-06-06 11:43 ` [PATCH v4 1/4] Bluetooth: net: add hci_iso_hdr function for iso data Chris Lu
2024-06-06 12:42 ` Bluetooth: btusb: MediaTek ISO data transmission bluez.test.bot
2024-06-06 20:10 ` [PATCH v4 1/4] Bluetooth: net: add hci_iso_hdr function for iso data Luiz Augusto von Dentz
2024-06-06 11:43 ` Chris Lu [this message]
2024-06-06 20:53 ` [PATCH v4 2/4] Bluetooth: btusb: add callback function in btusb suspend/resume Luiz Augusto von Dentz
2024-06-06 11:43 ` [PATCH v4 3/4] Bluetooth: btmtk: add macro to get/set/clear MediaTek defined flags Chris Lu
2024-06-06 11:43 ` [PATCH v4 4/4] Bluetooth: btusb: mediatek: add ISO data transmission functions Chris Lu
2024-06-06 21:06 ` Luiz Augusto von Dentz
2024-06-06 23:52 ` kernel test robot
2024-06-08 6:40 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240606114321.30515-3-chris.lu@mediatek.com \
--to=chris.lu@mediatek.com \
--cc=aaron.hou@mediatek.com \
--cc=deren.Wu@mediatek.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=sean.wang@mediatek.com \
--cc=steve.lee@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox