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 <bgoda...@codeaurora.org> > Tested-by: Matthias Kaehlcke <m...@chromium.org> > Reviewed-by: Matthias Kaehlcke <m...@chromium.org> > Signed-off-by: Matthias Kaehlcke <m...@chromium.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
