From: Marcel Holtmann <marcel@holtmann.org>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
Balakrishna Godavarthi <bgodavar@codeaurora.org>,
Hemantg <hemantg@codeaurora.org>
Subject: Re: [PATCH 0/2] Reduce delay after sending baudrate request for WCN3990
Date: Wed, 27 Feb 2019 08:48:31 +0100 [thread overview]
Message-ID: <45D9EB4B-C81A-4970-9ED1-3737A0AF771F@holtmann.org> (raw)
In-Reply-To: <20190226200848.154216-1-mka@chromium.org>
Hi Matthias,
> The current 300ms delay after a baudrate change is extremely long.
> For WCM3990 it is sufficient to wait 10ms after the baudrate change
> request has been sent over the wire.
>
> Also use msleep() instead of a set_current_state() / schedule_timeout()
> combo.
>
> Matthias Kaehlcke (2):
> hci_qca: Use msleep() instead of open coding it
> hci_qca: Reduce delay after sending baudrate request for WCN3990
>
> drivers/bluetooth/hci_qca.c | 30 +++++++++++++++++++++---------
> 1 file changed, 21 insertions(+), 9 deletions(-)
patch 1/2 has been applied to bluetooth-next tree. The patch 2/2 fails to apply.
Regards
Marcel
next prev parent reply other threads:[~2019-02-27 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 20:08 [PATCH 0/2] Reduce delay after sending baudrate request for WCN3990 Matthias Kaehlcke
2019-02-26 20:08 ` [PATCH 1/2] hci_qca: Use msleep() instead of open coding it Matthias Kaehlcke
2019-02-26 20:08 ` [PATCH 2/2] hci_qca: Reduce delay after sending baudrate request for WCN3990 Matthias Kaehlcke
2019-02-26 20:20 ` Matthias Kaehlcke
2019-02-27 7:48 ` Marcel Holtmann [this message]
2019-02-27 20:35 ` [PATCH 0/2] " Matthias Kaehlcke
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=45D9EB4B-C81A-4970-9ED1-3737A0AF771F@holtmann.org \
--to=marcel@holtmann.org \
--cc=bgodavar@codeaurora.org \
--cc=hemantg@codeaurora.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.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).