From: Conor Dooley <conor@kernel.org>
To: Hugo Osvaldo Barrera <hugo@whynothugo.nl>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Linus Walleij <linusw@kernel.org>,
linux-bluetooth@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: bluetooth: broadcom: add BCM43752
Date: Sun, 28 Jun 2026 20:17:36 +0100 [thread overview]
Message-ID: <20260628-shakable-spooky-e75e410f20f5@spud> (raw)
In-Reply-To: <20260628095500.29810-2-hugo@whynothugo.nl>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
On Sun, Jun 28, 2026 at 11:55:00AM +0200, Hugo Osvaldo Barrera wrote:
> Document the compatible string for BCM43752.
>
> Signed-off-by: Hugo Osvaldo Barrera <hugo@whynothugo.nl>
> ---
> .../devicetree/bindings/net/bluetooth/brcm,bluetooth.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/net/bluetooth/brcm,bluetooth.yaml b/Documentation/devicetree/bindings/net/bluetooth/brcm,bluetooth.yaml
> index 95501e858e6f..04e8a968548d 100644
> --- a/Documentation/devicetree/bindings/net/bluetooth/brcm,bluetooth.yaml
> +++ b/Documentation/devicetree/bindings/net/bluetooth/brcm,bluetooth.yaml
> @@ -29,6 +29,7 @@ properties:
> - brcm,bcm43438-bt
> - brcm,bcm4345c5
> - brcm,bcm43540-bt
> + - brcm,bcm43752-bt
This new compatible uses no match data. Why is a fallback compatible not
suitable?
Thanks,
Conor.
> - brcm,bcm4335a0
> - brcm,bcm4349-bt
> - cypress,cyw4373a0-bt
> --
> 2.54.0
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-06-28 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 9:54 [PATCH 1/2] Bluetooth: hci_bcm: add BCM43752 Hugo Osvaldo Barrera
2026-06-28 9:55 ` [PATCH 2/2] dt-bindings: bluetooth: broadcom: " Hugo Osvaldo Barrera
2026-06-28 16:49 ` Hugo Osvaldo Barrera
2026-06-28 19:16 ` Conor Dooley
2026-06-28 19:17 ` Conor Dooley [this message]
2026-06-28 11:57 ` [1/2] Bluetooth: hci_bcm: " 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=20260628-shakable-spooky-e75e410f20f5@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hugo@whynothugo.nl \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=robh@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