Hi Rafal, This same HS UART exists on all the bcmbca SoCs that listed in brcm,bcmbca.yaml. I suggest to use bcmbca for all instead of naming based on each individual chip. This will be consistent with spi, nand and other common periph blocks used in bcmbca SoCs. Thanks, William On 11/21/2023 04:13 AM, Rafał Miłecki wrote:
From: Rafał Miłecki <rafal@xxxxxxxxxx> It's an UART controller that first appeared on BCM63138 SoC and then was reused on other bcmbca familiy chipsets. Signed-off-by: Rafał Miłecki <rafal@xxxxxxxxxx> --- .../serial/brcm,bcm63138-hs-uart.yaml | 44 +++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 Documentation/devicetree/bindings/serial/brcm,bcm63138-hs-uart.yaml diff --git a/Documentation/devicetree/bindings/serial/brcm,bcm63138-hs-uart.yaml b/Documentation/devicetree/bindings/serial/brcm,bcm63138-hs-uart.yaml new file mode 100644 index 000000000000..91a7e945be39 --- /dev/null +++ b/Documentation/devicetree/bindings/serial/brcm,bcm63138-hs-uart.yaml @@ -0,0 +1,44 @@ +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/serial/brcm,bcm63138-hs-uart.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Broadcom's BCM63138 High Speed UART + +description: + High speed serial port controller that was designed to handle Bluetooth + devices communication. It supports sending custom frames that need to be + processed by a host system. + +maintainers: + - Rafał Miłecki <rafal@xxxxxxxxxx> + +allOf: + - $ref: serial.yaml# + +properties: + compatible: + const: brcm,bcm63138-hs-uart + + reg: + maxItems: 1 + + interrupts: + maxItems: 1 + +required: + - reg + - interrupts + +unevaluatedProperties: false + +examples: + - | + #include <dt-bindings/interrupt-controller/arm-gic.h> + + serial@fffec400 { + compatible = "brcm,bcm63138-hs-uart"; + reg = <0xfffec400 0x1e0>; + interrupts = <GIC_SPI 34 IRQ_TYPE_LEVEL_HIGH>; + };
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
