From: "André Eikmeyer" <dev@deq.rocks>
To: Myria Sarvay <myrialsarvay@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
sven@kernel.org, j@jannau.net, neal@gompa.dev,
asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Yossef Osman <Yossef.Osman@proton.me>,
Aditya Garg <aditya.garg@linux.dev>
Subject: Re: [PATCH v2 1/2] Bluetooth: btbcm: raise ACL priority on Apple Broadcom controllers
Date: Fri, 6 Nov 2026 08:33:39 +0100 [thread overview]
Message-ID: <20261106083339.677cc75d@kait2en-mbp15-1> (raw)
In-Reply-To: <au1uH6uxtsw2vHfP@macbookair>
On Fri, 6 Nov 2026 17:05:19 +1100
Myria Sarvay <myrialsarvay@gmail.com> wrote:
> Just wanted to point it out, if you hadn't seen it before, that Sasha
> has in the past sent a different patch [1] to run these priority
> commands. They seem to take a different approach to when to enable/run
> them. Wasn't sure if one was better or worse though.
Hi Myria,
thanks, indeed I hadn't seen it. Sasha's approach is the better one
IMO, it only raises the links that carry audio. The dropouts I measured
are on the BCM4364 of the MacBookPro15,1 and 16,x behind hci_bcm, which
only needs hci_set_brcm_capable() on Apple machines on top of Sasha's
patch.
Luiz, let me tinker. I'll drop 1/2 and send the hci_bcm part on top of
Sasha's patch once I've tested. Then we should have it nice and
consistent.
Andre
next prev parent reply other threads:[~2026-11-06 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 8:57 [PATCH v2 0/2] Bluetooth: Broadcom controllers of the Apple T2 Macs Andre Eikmeyer
2026-11-05 8:57 ` [PATCH v2 1/2] Bluetooth: btbcm: raise ACL priority on Apple Broadcom controllers Andre Eikmeyer
2026-11-06 6:05 ` Myria Sarvay
2026-11-06 7:33 ` André Eikmeyer [this message]
2026-11-06 9:40 ` Sasha Finkelstein
2026-11-06 10:39 ` André Eikmeyer
2026-11-06 10:53 ` Sasha Finkelstein
2026-11-06 11:12 ` André Eikmeyer
2026-11-06 15:06 ` André Eikmeyer
2026-11-05 8:57 ` [PATCH v2 2/2] Bluetooth: set the strict duplicate filter quirk " Andre Eikmeyer
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=20261106083339.677cc75d@kait2en-mbp15-1 \
--to=dev@deq.rocks \
--cc=Yossef.Osman@proton.me \
--cc=aditya.garg@linux.dev \
--cc=asahi@lists.linux.dev \
--cc=j@jannau.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=myrialsarvay@gmail.com \
--cc=neal@gompa.dev \
--cc=sven@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
all inboxes | Powered by JetHome®