All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <mka@chromium.org>
To: Marcel Holtmann <marcel@holtmann.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 12:35:55 -0800	[thread overview]
Message-ID: <20190227203555.GA192510@google.com> (raw)
In-Reply-To: <45D9EB4B-C81A-4970-9ED1-3737A0AF771F@holtmann.org>

Hi Marcel,

On Wed, Feb 27, 2019 at 08:48:31AM +0100, Marcel Holtmann wrote:
> 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.

Thanks!

> The patch 2/2 fails to apply.

Right, the series "Bluetooth: hci_qca: Add delay after power-off
pulse" that was just applied touches the same code. I'll send a
rebased version soon.

Cheers

Matthias

      reply	other threads:[~2019-02-27 20:35 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 ` [PATCH 0/2] " Marcel Holtmann
2019-02-27 20:35   ` Matthias Kaehlcke [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=20190227203555.GA192510@google.com \
    --to=mka@chromium.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=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.