linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Cc: BlueZ <linux-bluetooth@vger.kernel.org>,
	ChromeOS Bluetooth Upstreaming 
	<chromeos-bluetooth-upstreaming@chromium.org>,
	"David S. Miller" <davem@davemloft.net>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	netdev <netdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH 0/2] Bluetooth: Update LE scanning parameters for suspend
Date: Wed, 13 May 2020 08:51:45 +0200	[thread overview]
Message-ID: <037EB7A4-BC2B-4776-B911-423A72F763A3@holtmann.org> (raw)
In-Reply-To: <20200513020933.102443-1-abhishekpandit@chromium.org>

Hi Abhishek,

> This series updates the values used for window and interval when the
> system suspends. It also fixes a u8 vs u16 bug when setting up passive
> scanning.
> 
> The values chosen for window and interval are 11.25ms and 640ms. I have
> tested these on several Chromebooks with different LE peers (mouse,
> keyboard, Raspberry Pi running bluez) and all of them are able to wake
> the system with those parameters.
> 
> Thanks
> Abhishek
> 
> 
> 
> Abhishek Pandit-Subedi (2):
>  Bluetooth: Fix incorrect type for window and interval
>  Bluetooth: Modify LE window and interval for suspend
> 
> net/bluetooth/hci_request.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)

both patches have been applied to bluetooth-next tree.

Regards

Marcel


      parent reply	other threads:[~2020-05-13  6:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13  2:09 [PATCH 0/2] Bluetooth: Update LE scanning parameters for suspend Abhishek Pandit-Subedi
2020-05-13  2:09 ` [PATCH 1/2] Bluetooth: Fix incorrect type for window and interval Abhishek Pandit-Subedi
2020-05-13  2:09 ` [PATCH 2/2] Bluetooth: Modify LE window and interval for suspend Abhishek Pandit-Subedi
2020-05-13  6:51 ` Marcel Holtmann [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=037EB7A4-BC2B-4776-B911-423A72F763A3@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=abhishekpandit@chromium.org \
    --cc=chromeos-bluetooth-upstreaming@chromium.org \
    --cc=davem@davemloft.net \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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).