linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 204585] Bluetooth Mouse Polling Rate Regressed to 20hz
Date: Sun, 08 Sep 2019 11:56:02 +0000	[thread overview]
Message-ID: <bug-204585-62941-t1LZmG68jW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204585-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=204585

Leif Liddy (leif.liddy@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |leif.liddy@gmail.com

--- Comment #1 from Leif Liddy (leif.liddy@gmail.com) ---
I'm seeing this exact same issue with an orochi (2015) mouse on my laptop
running kernel 5.2.11
What'd odd is that this issue isn't present when using this mouse on my other
laptop running the same distro + kernel (but different bluetooth chipset).

Not sure when this issue started exactly, but it was either kernel 5.1.x or
5.2.x.  

The stated hcitool command solves the issue for me. Since hcitool is
deprecated, what is the 'proper' method we're meant to use to implement this
change?

I'm not able to change the polling intervals via debugfs as conn_min_interval
and conn_max_interval don't exist

# find /sys/kernel/debug/bluetooth/hci0 -type f 
/sys/kernel/debug/bluetooth/hci0/le_max_key_size
/sys/kernel/debug/bluetooth/hci0/le_min_key_size
/sys/kernel/debug/bluetooth/hci0/vendor_diag
/sys/kernel/debug/bluetooth/hci0/dut_mode

-- 
You are receiving this mail because:
You are the assignee for the bug.

  reply	other threads:[~2019-09-08 11:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14 18:22 [Bug 204585] New: Bluetooth Mouse Polling Rate Regressed to 20hz bugzilla-daemon
2019-09-08 11:56 ` bugzilla-daemon [this message]
2019-09-12 12:47 ` [Bug 204585] " bugzilla-daemon
2019-09-12 12:53 ` bugzilla-daemon
2019-09-14 13:17 ` bugzilla-daemon
2019-11-06 15:53 ` bugzilla-daemon

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=bug-204585-62941-t1LZmG68jW@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-bluetooth@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).