[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <C4C12227-FA4E-47F9-A161-6ADE490AAA91@holtmann.org>
Date: Fri, 11 Sep 2020 09:10:39 +0200
From: Marcel Holtmann <marcel@...tmann.org>
To: Venkata Lakshmi Narayana Gubba <gubbaven@...eaurora.org>
Cc: Johan Hedberg <johan.hedberg@...il.com>,
Matthias Kaehlcke <mka@...omium.org>,
open list <linux-kernel@...r.kernel.org>,
linux-bluetooth <linux-bluetooth@...r.kernel.org>,
Hemantg <hemantg@...eaurora.org>,
MSM <linux-arm-msm@...r.kernel.org>,
Balakrishna Godavarthi <bgodavar@...eaurora.org>,
rjliao@...eaurora.org, hbandi@...eaurora.org,
abhishekpandit@...omium.org
Subject: Re: [RESEND v1 0/2] Close UART port if NON_PERSISTENT_SETUP is set
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
Powered by blists - more mailing lists