From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sven Peter <sven@svenpeter.dev>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Hector Martin <marcan@marcan.st>,
Alyssa Rosenzweig <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 v2 2/5] dt-bindings: net: Add Broadcom BCM4377 family PCIe Bluetooth
Date: Thu, 8 Sep 2022 13:19:17 +0200 [thread overview]
Message-ID: <bcb799ea-d58e-70dc-c5c2-daaff1b19bf5@linaro.org> (raw)
In-Reply-To: <20220907170935.11757-3-sven@svenpeter.dev>
On 07/09/2022 19:09, 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>
> ---
> changes from v1:
> - added apple,* pattern to brcm,board-type
> - s/PCI/PCIe/
> - fixed 1st reg cell inside the example to not contain the bus number
>
> .../bindings/net/brcm,bcm4377-bluetooth.yaml | 78 +++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 79 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..fb851f8e6bcb
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/brcm,bcm4377-bluetooth.yaml
> @@ -0,0 +1,78 @@
> +# 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 PCIe Bluetooth Chips
> +
> +allOf:
> + - $ref: bluetooth-controller.yaml#
Put it before properties (so after description).
> +
> +maintainers:
> + - Sven Peter <sven@svenpeter.dev>
> +
> +description:
> + This binding describes Broadcom BCM4377 family PCIe-attached bluetooth chips
> + 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.
maxItems: X
> +
> + 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,.*'
> +
> + brcm,taurus-cal-blob:
> + $ref: /schemas/types.yaml#/definitions/uint8-array
> + description: A per-device calibration blob for the Bluetooth radio. This
> + should be filled in by the bootloader from platform configuration
> + data, if necessary, and will be uploaded to the device.
> + This blob is used if the chip stepping of the Bluetooth module does not
> + support beamforming.
Isn't it:
s/beamforming/beam forming/
?
> +
> + brcm,taurus-bf-cal-blob:
> + $ref: /schemas/types.yaml#/definitions/uint8-array
> + description: A per-device calibration blob for the Bluetooth radio. This
> + should be filled in by the bootloader from platform configuration
> + data, if necessary, and will be uploaded to the device.
> + This blob is used if the chip stepping of the Bluetooth module supports
> + beamforming.
Same here.
> +
> + local-bd-address: true
> +
> +required:
> + - compatible
> + - reg
> + - local-bd-address
> + - brcm,board-type
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + pcie {
> + #address-cells = <3>;
> + #size-cells = <2>;
> +
> + bluetooth@0,1 {
The unit address seems to be different than reg.
> + compatible = "pci14e4,5f69";
> + reg = <0x100 0x0 0x0 0x0 0x0>;
> + brcm,board-type = "apple,honshu";
> + /* To be filled by the bootloader */
> + local-bd-address = [00 00 00 00 00 00];
> + };
> + };
Best regards,
Krzysztof
_______________________________________________
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-09-08 11:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 17:09 [PATCH v2 0/5] Broadcom/Apple Bluetooth driver for Apple Silicon Sven Peter
2022-09-07 17:09 ` [PATCH v2 1/5] dt-bindings: net: Add generic Bluetooth controller Sven Peter
2022-09-08 11:16 ` Krzysztof Kozlowski
2022-09-19 15:15 ` Sven Peter
2022-09-07 17:09 ` [PATCH v2 2/5] dt-bindings: net: Add Broadcom BCM4377 family PCIe Bluetooth Sven Peter
2022-09-08 11:19 ` Krzysztof Kozlowski [this message]
2022-09-08 11:29 ` Martin Povišer
2022-09-08 11:34 ` Krzysztof Kozlowski
2022-09-08 11:30 ` Hector Martin
2022-09-12 21:12 ` Rob Herring
2022-09-15 13:09 ` Rob Herring
2022-09-19 15:15 ` Sven Peter
2022-09-07 17:09 ` [PATCH v2 3/5] Bluetooth: hci_event: Add quirk to ignore byte in LE Extended Adv Report Sven Peter
2022-09-07 18:49 ` Luiz Augusto von Dentz
2022-09-07 19:21 ` Sven Peter
2022-09-07 17:09 ` [PATCH v2 4/5] Bluetooth: Add quirk to disable extended scanning Sven Peter
2022-09-07 17:09 ` [PATCH v2 5/5] Bluetooth: hci_bcm4377: Add new driver for BCM4377 PCI boards 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=bcb799ea-d58e-70dc-c5c2-daaff1b19bf5@linaro.org \
--to=krzysztof.kozlowski@linaro.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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).