Linux bluetooth development
 help / color / mirror / Atom feed
From: Sven Peter <sven@kernel.org>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>,
	Janne Grunau <j@jannau.net>, Neal Gompa <neal@gompa.dev>,
	Marcel Holtmann <marcel@holtmann.org>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
	asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_bcm4377: Ignore reserved PHY in ext adv reports on BCM4378
Date: Tue, 18 Aug 2026 12:18:31 +0200	[thread overview]
Message-ID: <63b6eb28-dc1b-4e51-89c0-1591ff216da5@kernel.org> (raw)
In-Reply-To: <20260818-fix-bcm4378-ext-adv-v1-1-81a143eac194@kernel.org>

On 18.08.26 11:49, Lorenzo Stoakes (ARM) wrote:
> Commit ed2a2ef16a6b ("Bluetooth: Add quirk to ignore reserved PHY bits in
> LE Extended Adv Report") added a quirk to handle creative use of the
> reserved bits in the PHY fields for 4388 controllers in Apple silicon.
> 
> I observed the same issue with the BCM4378 Bluetooth controller (14e4:5f69,
> rev 05) on an Apple MacBook Pro (13-inch, M2, 2022):
> 
>> HCI Event: LE Meta Event (0x3e) plen 51
>        LE Extended Advertising Report (0x0d)
>          Num reports: 1
>          Entry 0
>            Event type: 0x2513
>              Props: 0x0013
>                Connectable
>                Scannable
>                Use legacy advertising PDUs
>              Data status: Complete
>              Reserved (0x2500)
>            Legacy PDU Type: Reserved (0x2513)
>            Address type: Random (0x01)
>            Address: EA:C1:82:F0:24:C6 (Static)
>            Primary PHY: Reserved
>            Secondary PHY: No packets
>            SID: no ADI field (0xff)
>            TX power: 127 dBm
>            RSSI: -57 dBm (0xc7)
>            Periodic advertising interval: 0.00 msec (0x0000)
>            Direct address type: Public (0x00)
>            Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
>            Data length: 25
> 
> This results in the firmware rejecting connection attempts with
> "Unsupported Feature or Parameter Value" (0x11).
> 
> Fix the issue by using the same quirk for BCM4378 devices too.
> 
> I tested this locally and confirmed that the issue is resolved.
> 
> This was observed when attempting to connect a Kinesis Advantage 360
> keyboard to the MacBook.
> 
> Assisted-by: Claude:claude-fable-5
> Fixes: 2e7ed5f5e69b ("Bluetooth: hci_sync: Use advertised PHYs on hci_le_ext_create_conn_sync")
> Cc: stable@vger.kernel.org
> Signed-off-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
> ---

Reviewed-by: Sven Peter <sven@kernel.org>

Kinda surprised no one ran into this so far tbh.


Best,


Sven



  reply	other threads:[~2026-08-18 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18  9:49 [PATCH] Bluetooth: hci_bcm4377: Ignore reserved PHY in ext adv reports on BCM4378 Lorenzo Stoakes (ARM)
2026-08-18 10:18 ` Sven Peter [this message]
2026-08-18 10:37 ` 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=63b6eb28-dc1b-4e51-89c0-1591ff216da5@kernel.org \
    --to=sven@kernel.org \
    --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=ljs@kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=luiz.von.dentz@intel.com \
    --cc=marcel@holtmann.org \
    --cc=neal@gompa.dev \
    --cc=stable@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