From: Marcel Holtmann <marcel@holtmann.org>
To: Venkata Lakshmi Narayana Gubba <gubbaven@codeaurora.org>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
Matthias Kaehlcke <mka@chromium.org>,
open list <linux-kernel@vger.kernel.org>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
Hemantg <hemantg@codeaurora.org>,
MSM <linux-arm-msm@vger.kernel.org>,
Balakrishna Godavarthi <bgodavar@codeaurora.org>,
rjliao@codeaurora.org, hbandi@codeaurora.org,
abhishekpandit@chromium.org
Subject: Re: [RESEND v1 0/2] Close UART port if NON_PERSISTENT_SETUP is set
Date: Fri, 11 Sep 2020 09:10:39 +0200 [thread overview]
Message-ID: <C4C12227-FA4E-47F9-A161-6ADE490AAA91@holtmann.org> (raw)
In-Reply-To: <1599733843-20311-1-git-send-email-gubbaven@codeaurora.org>
Hi Venkata,
> When HCI_QUIRK_NON_PERSISTENT_SETUP is set by drivers,
> it indicates that BT SoC will be completely powered OFF
> during BT OFF. On next BT ON firmware must be downloaded
> again. Holding UART port open during BT OFF is draining
> the battery. Now during BT OFF, UART port is closed if
> qurik HCI_QUIRK_NON_PERSISTENT_SETUP is set by clearing
> HCI_UART_PROTO_READY proto flag. On next BT ON, UART
> port is opened if HCI_UART_PROTO_READY proto flag is cleared.
>
> Venkata Lakshmi Narayana Gubba (2):
> Bluetooth: hci_serdev: Close UART port if NON_PERSISTENT_SETUP is set
> Bluetooth: hci_qca: Remove duplicate power off in proto close
>
> drivers/bluetooth/hci_qca.c | 5 ++---
> drivers/bluetooth/hci_serdev.c | 36 +++++++++++++++++++++++++++++++++---
> 2 files changed, 35 insertions(+), 6 deletions(-)
both patches have been applied to bluetooth-next tree.
Regards
Marcel
prev parent reply other threads:[~2020-09-11 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 10:30 [RESEND v1 0/2] Close UART port if NON_PERSISTENT_SETUP is set Venkata Lakshmi Narayana Gubba
2020-09-10 10:30 ` [RESEND v1 1/2] Bluetooth: hci_serdev: " Venkata Lakshmi Narayana Gubba
2020-09-10 10:30 ` [RESEND v1 2/2] Bluetooth: hci_qca: Remove duplicate power off in proto close Venkata Lakshmi Narayana Gubba
2020-09-11 7:10 ` Marcel Holtmann [this message]
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=C4C12227-FA4E-47F9-A161-6ADE490AAA91@holtmann.org \
--to=marcel@holtmann.org \
--cc=abhishekpandit@chromium.org \
--cc=bgodavar@codeaurora.org \
--cc=gubbaven@codeaurora.org \
--cc=hbandi@codeaurora.org \
--cc=hemantg@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=mka@chromium.org \
--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).