From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 0887e7: test: functional: change the HoG connection rate f...
Date: Mon, 12 Oct 2026 10:51:37 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1184010/000000-0887e7@github.com> (raw)
Branch: refs/heads/1184010
Home: https://github.com/bluez/bluez
Commit: 0887e798bee43488d067ef3209768b7b72685060
https://github.com/bluez/bluez/commit/0887e798bee43488d067ef3209768b7b72685060
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-10-12 (Mon, 12 Oct 2026)
Changed paths:
M doc/functional-hog.rst
M test/functional/test_hog.py
Log Message:
-----------
test: functional: change the HoG connection rate from the HID device
As specified by the HIDS/HOGP SCI FIPD, the HID device initiates the
Connection Rate Update procedure once the HID host writes the mode to
the HID Control Point, so load the connection subrate on the HID device
instead of the HID host.
This requires the kernel to issue the LE Connection Rate Request as
peripheral.
Assisted-by: OpenCode:claude-opus-5.5
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-10-12 17:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1184010/000000-0887e7@github.com \
--to=noreply@github.com \
--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