From: Tarjei <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] dc3162: adapter: Add configurable default LE PHYs
Date: Mon, 25 May 2026 03:18:55 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1100262/000000-dc3162@github.com> (raw)
Branch: refs/heads/1100262
Home: https://github.com/bluez/bluez
Commit: dc316288b2356b3b2285ef20851b4aa4a112764f
https://github.com/bluez/bluez/commit/dc316288b2356b3b2285ef20851b4aa4a112764f
Author: Tarjei Bitustøyl <tarjeib@gmail.com>
Date: 2026-05-25 (Mon, 25 May 2026)
Changed paths:
M src/adapter.c
M src/btd.h
M src/main.c
M src/main.conf
Log Message:
-----------
adapter: Add configurable default LE PHYs
Some controllers mis-handle LE procedures on specific PHYs with
certain peers. On an Intel AX210-class controller, connecting to a
Frostbay BLE device can fail during early ATT/GATT setup unless the
adapter is limited to LE 1M TX/RX.
Add an opt-in [LE] DefaultPHYs setting to bluetoothd and apply it at
adapter startup using MGMT_OP_GET/SET_PHY_CONFIGURATION while
preserving non-configurable PHY bits.
This provides a generic, adapter-wide workaround for controller-
specific LE PHY interoperability problems affecting scanning and
connection establishment, without adding device-specific quirks.
v2:
- Check MGMT_SETTING_PHY_CONFIGURATION before sending PHY
configuration commands.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-05-25 10:18 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/1100262/000000-dc3162@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