From: Rob Herring <robh@kernel.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: sven@svenpeter.dev, marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, krzysztof.kozlowski+dt@linaro.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, marcan@marcan.st, alyssa@rosenzweig.io,
asahi@lists.linux.dev, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] dt-bindings: net: Add Broadcom BCM4377 family PCI Bluetooth
Date: Wed, 10 Aug 2022 12:10:12 -0600 [thread overview]
Message-ID: <20220810181012.GC200295-robh@kernel.org> (raw)
In-Reply-To: <d3ce6343fdaaf127@bloch.sibelius.xs4all.nl>
On Mon, Aug 01, 2022 at 05:51:23PM +0200, Mark Kettenis wrote:
> > Date: Mon, 1 Aug 2022 09:39:21 -0600
> > From: Rob Herring <robh@kernel.org>
> >
> > On Mon, Aug 01, 2022 at 12:36:30PM +0200, Sven Peter wrote:
> > > These chips are combined Wi-Fi/Bluetooth radios which expose a
> > > PCI subfunction for the Bluetooth part.
> > > They are found in Apple machines such as the x86 models with the T2
> > > chip or the arm64 models with the M1 or M2 chips.
> > >
> > > Signed-off-by: Sven Peter <sven@svenpeter.dev>
> > > ---
> > > .../bindings/net/brcm,bcm4377-bluetooth.yaml | 77 +++++++++++++++++++
> > > MAINTAINERS | 1 +
> > > 2 files changed, 78 insertions(+)
> > > create mode 100644 Documentation/devicetree/bindings/net/brcm,bcm4377-bluetooth.yaml
> > >
> > > diff --git a/Documentation/devicetree/bindings/net/brcm,bcm4377-bluetooth.yaml b/Documentation/devicetree/bindings/net/brcm,bcm4377-bluetooth.yaml
> > > new file mode 100644
> > > index 000000000000..afe6ecebd939
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/net/brcm,bcm4377-bluetooth.yaml
> > > @@ -0,0 +1,77 @@
> > > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > > +%YAML 1.2
> > > +---
> > > +$id: http://devicetree.org/schemas/net/brcm,bcm4377-bluetooth.yaml#
> > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > +
> > > +title: Broadcom BCM4377 family PCI Bluetooth Chips
> > > +
> > > +allOf:
> > > + - $ref: bluetooth-controller.yaml#
> > > +
> > > +maintainers:
> > > + - Sven Peter <sven@svenpeter.dev>
> > > +
> > > +description:
> > > + This binding describes Broadcom BCM4377 family PCI-attached bluetooth chips
> >
> > s/PCI/PCIe/
> >
> > > + usually found in Apple machines. The Wi-Fi part of the chip is described in
> > > + bindings/net/wireless/brcm,bcm4329-fmac.yaml.
> > > +
> > > +properties:
> > > + compatible:
> > > + enum:
> > > + - pci14e4,5fa0 # BCM4377
> > > + - pci14e4,5f69 # BCM4378
> > > + - pci14e4,5f71 # BCM4387
> > > +
> > > + reg:
> > > + description: PCI device identifier.
> > > +
> > > + brcm,board-type:
> > > + $ref: /schemas/types.yaml#/definitions/string
> > > + description: Board type of the Bluetooth chip. This is used to decouple
> > > + the overall system board from the Bluetooth module and used to construct
> > > + firmware and calibration data filenames.
> > > + On Apple platforms, this should be the Apple module-instance codename
> > > + prefixed by "apple,", e.g. "apple,atlantisb".
> >
> > pattern: '^apple,.*'
> >
> > And when there's other known vendors we can add them.
> >
> > Really, I'm not all that crazy about this property. 'firmware-name'
> > doesn't work? Or perhaps this should just be a more specific compatible
> > string.
>
> This matches the property proposed here:
>
> https://patchwork.kernel.org/project/linux-wireless/patch/20220104072658.69756-2-marcan@marcan.st/
>
> Unfortunately that series didn't make progress for other reasons...
>
> There was some significant bikeshedding in the original version of that series already:
>
> https://patchwork.kernel.org/project/linux-wireless/patch/20211226153624.162281-2-marcan@marcan.st/
>
> Are you sure you want to repeat that? ;)
No, it's fine. :)
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: sven@svenpeter.dev, marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, krzysztof.kozlowski+dt@linaro.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, marcan@marcan.st, alyssa@rosenzweig.io,
asahi@lists.linux.dev, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] dt-bindings: net: Add Broadcom BCM4377 family PCI Bluetooth
Date: Wed, 10 Aug 2022 12:10:12 -0600 [thread overview]
Message-ID: <20220810181012.GC200295-robh@kernel.org> (raw)
In-Reply-To: <d3ce6343fdaaf127@bloch.sibelius.xs4all.nl>
On Mon, Aug 01, 2022 at 05:51:23PM +0200, Mark Kettenis wrote:
> > Date: Mon, 1 Aug 2022 09:39:21 -0600
> > From: Rob Herring <robh@kernel.org>
> >
> > On Mon, Aug 01, 2022 at 12:36:30PM +0200, Sven Peter wrote:
> > > These chips are combined Wi-Fi/Bluetooth radios which expose a
> > > PCI subfunction for the Bluetooth part.
> > > They are found in Apple machines such as the x86 models with the T2
> > > chip or the arm64 models with the M1 or M2 chips.
> > >
> > > Signed-off-by: Sven Peter <sven@svenpeter.dev>
> > > ---
> > > .../bindings/net/brcm,bcm4377-bluetooth.yaml | 77 +++++++++++++++++++
> > > MAINTAINERS | 1 +
> > > 2 files changed, 78 insertions(+)
> > > create mode 100644 Documentation/devicetree/bindings/net/brcm,bcm4377-bluetooth.yaml
> > >
> > > diff --git a/Documentation/devicetree/bindings/net/brcm,bcm4377-bluetooth.yaml b/Documentation/devicetree/bindings/net/brcm,bcm4377-bluetooth.yaml
> > > new file mode 100644
> > > index 000000000000..afe6ecebd939
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/net/brcm,bcm4377-bluetooth.yaml
> > > @@ -0,0 +1,77 @@
> > > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > > +%YAML 1.2
> > > +---
> > > +$id: http://devicetree.org/schemas/net/brcm,bcm4377-bluetooth.yaml#
> > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > +
> > > +title: Broadcom BCM4377 family PCI Bluetooth Chips
> > > +
> > > +allOf:
> > > + - $ref: bluetooth-controller.yaml#
> > > +
> > > +maintainers:
> > > + - Sven Peter <sven@svenpeter.dev>
> > > +
> > > +description:
> > > + This binding describes Broadcom BCM4377 family PCI-attached bluetooth chips
> >
> > s/PCI/PCIe/
> >
> > > + usually found in Apple machines. The Wi-Fi part of the chip is described in
> > > + bindings/net/wireless/brcm,bcm4329-fmac.yaml.
> > > +
> > > +properties:
> > > + compatible:
> > > + enum:
> > > + - pci14e4,5fa0 # BCM4377
> > > + - pci14e4,5f69 # BCM4378
> > > + - pci14e4,5f71 # BCM4387
> > > +
> > > + reg:
> > > + description: PCI device identifier.
> > > +
> > > + brcm,board-type:
> > > + $ref: /schemas/types.yaml#/definitions/string
> > > + description: Board type of the Bluetooth chip. This is used to decouple
> > > + the overall system board from the Bluetooth module and used to construct
> > > + firmware and calibration data filenames.
> > > + On Apple platforms, this should be the Apple module-instance codename
> > > + prefixed by "apple,", e.g. "apple,atlantisb".
> >
> > pattern: '^apple,.*'
> >
> > And when there's other known vendors we can add them.
> >
> > Really, I'm not all that crazy about this property. 'firmware-name'
> > doesn't work? Or perhaps this should just be a more specific compatible
> > string.
>
> This matches the property proposed here:
>
> https://patchwork.kernel.org/project/linux-wireless/patch/20220104072658.69756-2-marcan@marcan.st/
>
> Unfortunately that series didn't make progress for other reasons...
>
> There was some significant bikeshedding in the original version of that series already:
>
> https://patchwork.kernel.org/project/linux-wireless/patch/20211226153624.162281-2-marcan@marcan.st/
>
> Are you sure you want to repeat that? ;)
No, it's fine. :)
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-10 18:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 10:36 [PATCH 0/5] Broadcom/Apple Bluetooth driver for Apple Silicon Sven Peter
2022-08-01 10:36 ` Sven Peter
2022-08-01 10:36 ` [PATCH 1/5] dt-bindings: net: Add generic Bluetooth controller Sven Peter
2022-08-01 10:36 ` Sven Peter
2022-08-01 11:15 ` Broadcom/Apple Bluetooth driver for Apple Silicon bluez.test.bot
2022-08-01 15:23 ` [PATCH 1/5] dt-bindings: net: Add generic Bluetooth controller Rob Herring
2022-08-01 15:23 ` Rob Herring
2022-08-01 17:35 ` Sven Peter
2022-08-01 17:35 ` Sven Peter
2022-08-01 10:36 ` [PATCH 2/5] dt-bindings: net: Add Broadcom BCM4377 family PCI Bluetooth Sven Peter
2022-08-01 10:36 ` Sven Peter
2022-08-01 15:39 ` Rob Herring
2022-08-01 15:39 ` Rob Herring
2022-08-01 15:51 ` Mark Kettenis
2022-08-01 15:51 ` Mark Kettenis
2022-08-10 18:10 ` Rob Herring [this message]
2022-08-10 18:10 ` Rob Herring
2022-08-01 10:36 ` [PATCH 3/5] Bluetooth: hci_event: Add quirk to ignore byte in LE Extended Adv Report Sven Peter
2022-08-01 10:36 ` Sven Peter
2022-08-01 10:36 ` [PATCH 4/5] Bluetooth: Add quirk to disable extended scanning Sven Peter
2022-08-01 10:36 ` Sven Peter
2022-08-01 10:36 ` [PATCH 5/5] Bluetooth: hci_bcm4377: Add new driver for BCM4377 PCI boards Sven Peter
2022-08-01 10:36 ` Sven Peter
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=20220810181012.GC200295-robh@kernel.org \
--to=robh@kernel.org \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=johan.hedberg@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--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=marcan@marcan.st \
--cc=marcel@holtmann.org \
--cc=mark.kettenis@xs4all.nl \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sven@svenpeter.dev \
/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.