[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <AE7AB525-CFAC-411E-A615-54AF4E6B645E@holtmann.org>
Date: Sat, 6 Jul 2019 12:51:16 +0200
From: Marcel Holtmann <marcel@...tmann.org>
To: Matthias Kaehlcke <mka@...omium.org>
Cc: Johan Hedberg <johan.hedberg@...il.com>,
linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
Balakrishna Godavarthi <bgodavar@...eaurora.org>,
Harish Bandi <c-hbandi@...eaurora.org>,
Rocky Liao <rjliao@...eaurora.org>
Subject: Re: [PATCH v9] Bluetooth: btqca: inject command complete event during
fw download
Hi Matthias,
> Latest qualcomm chips are not sending an command complete event for
> every firmware packet sent to chip. They only respond with a vendor
> specific event for the last firmware packet. This optimization will
> decrease the BT ON time. Due to this we are seeing a timeout error
> message logs on the console during firmware download. Now we are
> injecting a command complete event once we receive an vendor specific
> event for the last RAM firmware packet.
>
> Signed-off-by: Balakrishna Godavarthi <bgodavar@...eaurora.org>
> Tested-by: Matthias Kaehlcke <mka@...omium.org>
> Reviewed-by: Matthias Kaehlcke <mka@...omium.org>
> Signed-off-by: Matthias Kaehlcke <mka@...omium.org>
> ---
> Changes in v9:
> - define QCA_HCI_CC_SUCCESS (again)
> - use QCA_HCI_CC_OPCODE instead of HCI_OP_NOP
>
> Changes in v8:
> - renamed QCA_HCI_CC_SUCCESS to QCA_HCI_CC_OPCODE
> - use 0xFC00 as opcode of the injected event instead of 0
> - added Matthias' tags from the v7 review
> ---
> drivers/bluetooth/btqca.c | 39 ++++++++++++++++++++++++++++++++++++++-
> drivers/bluetooth/btqca.h | 4 ++++
> 2 files changed, 42 insertions(+), 1 deletion(-)
patch has been applied to bluetooth-next tree.
Regards
Marcel
Powered by blists - more mailing lists