linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Panicker Harish <quic_pharish@quicinc.com>
To: marcel@holtmann.org, johan.hedberg@gmail.com
Cc: mka@chromium.org, linux-kernel@vger.kernel.org,
	linux-bluetooth@vger.kernel.org, quic_hemantg@quicinc.com,
	linux-arm-msm@vger.kernel.org, quic_bgodavar@quicinc.com,
	rjliao@codeaurora.org, hbandi@codeaurora.org,
	abhishekpandit@chromium.org, mcchou@chromium.org,
	quic_saluvala@quicinc.com,
	Panicker Harish <quic_pharish@quicinc.com>
Subject: [PATCH v2] Bluetooth: hci_qca: Stop IBS timer during BT OFF
Date: Mon, 13 Dec 2021 11:01:36 +0530	[thread overview]
Message-ID: <1639373496-28009-1-git-send-email-quic_pharish@quicinc.com> (raw)

This change stops IBS timers during BT OFF.

Signed-off-by: Panicker Harish <quic_pharish@quicinc.com>

v2:
  * Addressed the username
  * The full implementation of IBS is based on timers
    to that reason I have used timers.

v1: initial patch
---
 drivers/bluetooth/hci_qca.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c
index dd768a8..6f44b26 100644
--- a/drivers/bluetooth/hci_qca.c
+++ b/drivers/bluetooth/hci_qca.c
@@ -1928,6 +1928,9 @@ static int qca_power_off(struct hci_dev *hdev)
 	hu->hdev->hw_error = NULL;
 	hu->hdev->cmd_timeout = NULL;
 
+	mod_timer(&qca->tx_idle_timer, 0);
+	mod_timer(&qca->wake_retrans_timer, 0);
+
 	/* Stop sending shutdown command if soc crashes. */
 	if (soc_type != QCA_ROME
 		&& qca->memdump_state == QCA_MEMDUMP_IDLE) {
-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc.


             reply	other threads:[~2021-12-13  5:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13  5:31 Panicker Harish [this message]
2021-12-13 15:07 ` [PATCH v2] Bluetooth: hci_qca: Stop IBS timer during BT OFF Matthias Kaehlcke
2021-12-14 11:49   ` PANICKER HARISH (Temp) (QUIC)

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=1639373496-28009-1-git-send-email-quic_pharish@quicinc.com \
    --to=quic_pharish@quicinc.com \
    --cc=abhishekpandit@chromium.org \
    --cc=hbandi@codeaurora.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mcchou@chromium.org \
    --cc=mka@chromium.org \
    --cc=quic_bgodavar@quicinc.com \
    --cc=quic_hemantg@quicinc.com \
    --cc=quic_saluvala@quicinc.com \
    --cc=rjliao@codeaurora.org \
    /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;
as well as URLs for NNTP newsgroup(s).