From: Kyle Pepper <cochcoder@proton.me>
To: linux-bluetooth@vger.kernel.org
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Subject: [PATCH v3] asha: allow LE 2M PHY on the audio channel
Date: Thu, 29 Oct 2026 03:00:53 +0000 [thread overview]
Message-ID: <20261029030037.1300725-1-cochcoder@proton.me> (raw)
Allow LE 2M alongside LE 1M on the connected audio socket before starting
ASHA. Keep streaming if the kernel cannot set the PHY preference.
Assisted-by: OpenCode:gpt-6.1-sol
Assisted-by: Codex:GPT-6
---
Changes since v2:
- Drop the standalone PHY unit test and its build/ignore entries.
- Reuse the existing test/simple-asha playback script.
Validation: builds without warnings, 35/35 native unit binaries,
and checkpatch pass.
profiles/audio/asha.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/profiles/audio/asha.c b/profiles/audio/asha.c
index 8e625fd..d862247 100644
--- a/profiles/audio/asha.c
+++ b/profiles/audio/asha.c
@@ -88,6 +88,8 @@ static void connect_cb(GIOChannel *io, GError *err, gpointer user_data)
struct connect_data *conn_data = user_data;
struct bt_asha_device *asha_dev = conn_data->asha_dev;
GError *gerr = NULL;
+ uint32_t phys;
+ int fd;
if (err) {
error("%s", err->message);
@@ -105,6 +107,15 @@ static void connect_cb(GIOChannel *io, GError *err, gpointer user_data)
g_error_free(gerr);
}
+ /*
+ * Allow LE 2M with LE 1M fallback. Older kernels may lack BT_PHY.
+ */
+ phys = BT_PHY_LE_1M_TX | BT_PHY_LE_1M_RX |
+ BT_PHY_LE_2M_TX | BT_PHY_LE_2M_RX;
+ fd = g_io_channel_unix_get_fd(io);
+ if (setsockopt(fd, SOL_BLUETOOTH, BT_PHY, &phys, sizeof(phys)) < 0)
+ DBG("Could not set LE 2M PHY preference: %s", strerror(errno));
+
asha_dev->io = io;
bt_asha_start(asha_dev->asha, conn_data->cb,
base-commit: 82667d713949447d7c94725432c61b33689ae68a
--
2.56.0
next reply other threads:[~2026-10-29 3:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 3:00 Kyle Pepper [this message]
2026-10-29 6:31 ` [v3] asha: allow LE 2M PHY on the audio channel bluez.test.bot
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=20261029030037.1300725-1-cochcoder@proton.me \
--to=cochcoder@proton.me \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.