From: fdanis-oss <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] d76c66: btio: add BT_IO_OPT_FORCE_ACTIVE support for L2CAP...
Date: Thu, 03 Sep 2026 08:00:07 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1157040/000000-5bf564@github.com> (raw)
Branch: refs/heads/1157040
Home: https://github.com/bluez/bluez
Commit: d76c663e701c5685230217496bf43977b3536d83
https://github.com/bluez/bluez/commit/d76c663e701c5685230217496bf43977b3536d83
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-03 (Thu, 03 Sep 2026)
Changed paths:
M btio/btio.c
M btio/btio.h
Log Message:
-----------
btio: add BT_IO_OPT_FORCE_ACTIVE support for L2CAP sockets
Introduce BT_IO_OPT_FORCE_ACTIVE in btio and plumb it through option
parsing and L2CAP setup.
When set, btio now programs BT_POWER on the underlying socket, allowing
callers to explicitly control force-active behavior.
Co-developed-by: Zhongjun.Yu@quectel.com
Signed-off-by: Zhongjun.Yu@quectel.com
Commit: 5bf5646d6c16b447d65f0d3ccac946f6bb5b5d62
https://github.com/bluez/bluez/commit/5bf5646d6c16b447d65f0d3ccac946f6bb5b5d62
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-03 (Thu, 03 Sep 2026)
Changed paths:
M profiles/input/device.c
Log Message:
-----------
profiles/input: disable force-active for Nintendo Switch Pro v1
For Nintendo Switch Pro v1 controllers (VID:PID 057e:2009), set
BT_IO_OPT_FORCE_ACTIVE to BT_POWER_FORCE_ACTIVE_OFF on the HID interrupt
channel during connection setup.
This avoids repeated host-triggered Exit Sniff requests and reduces
Sniff/Exit Sniff churn linked to unexpected disconnects.
Co-developed-by: Zhongjun.Yu@quectel.com
Signed-off-by: Zhongjun.Yu@quectel.com
Compare: https://github.com/bluez/bluez/compare/d76c663e701c%5E...5bf5646d6c16
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-03 15:00 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/1157040/000000-5bf564@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