[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6c51427a-98e2-0bbe-8f4b-37a4d9cacec7@canonical.com>
Date: Wed, 16 Feb 2022 17:13:30 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>, vkoul@...nel.org
Cc: robh+dt@...nel.org, sean.wang@...iatek.com, matthias.bgg@...il.com,
long.cheng@...iatek.com, dmaengine@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH v2] dt-bindings: dma: Convert mtk-uart-apdma to DT schema
On 16/02/2022 16:13, AngeloGioacchino Del Regno wrote:
> Convert the MediaTek UART APDMA Controller binding to DT schema.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
> ---
> v2: Fixed interrupt maxItems to 16, added interrupts/reg maxItems constraint
> to 8 when the dma-requests property is not present
>
> .../bindings/dma/mediatek,uart-dma.yaml | 123 ++++++++++++++++++
> .../bindings/dma/mtk-uart-apdma.txt | 56 --------
> 2 files changed, 123 insertions(+), 56 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/dma/mediatek,uart-dma.yaml
> delete mode 100644 Documentation/devicetree/bindings/dma/mtk-uart-apdma.txt
>
> diff --git a/Documentation/devicetree/bindings/dma/mediatek,uart-dma.yaml b/Documentation/devicetree/bindings/dma/mediatek,uart-dma.yaml
> new file mode 100644
> index 000000000000..67dbb2fed74c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/dma/mediatek,uart-dma.yaml
> @@ -0,0 +1,123 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/dma/mediatek,uart-dma.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MediaTek UART APDMA controller
> +
> +maintainers:
> + - Long Cheng <long.cheng@...iatek.com>
> +
> +description: |
> + The MediaTek UART APDMA controller provides DMA capabilities
> + for the UART peripheral bus.
> +
> +allOf:
> + - $ref: "dma-controller.yaml#"
> +
> +properties:
> + compatible:
> + oneOf:
> + - items:
> + - enum:
> + - mediatek,mt2712-uart-dma
> + - mediatek,mt8516-uart-dma
> + - const: mediatek,mt6577-uart-dma
> + - enum:
> + - mediatek,mt6577-uart-dma
> +
> + reg:
> + minItems: 1
> + maxItems: 16
> +
> + interrupts:
> + description: |
> + TX, RX interrupt lines for each UART APDMA channel
> + minItems: 1
> + maxItems: 16
> +
> + clocks:
> + description: Must contain one entry for the APDMA main clock
> + maxItems: 1
> +
> + clock-names:
> + const: apdma
> +
> + "#dma-cells":
> + const: 1
> + description: |
> + The first cell specifies the UART APDMA channel number
> +
> + dma-requests:
> + description: |
> + Number of virtual channels of the UART APDMA controller
> + maximum: 16
> +
> + mediatek,dma-33bits:
> + type: boolean
> + description: Enable 33-bits UART APDMA support
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +additionalProperties: false
> +
> +if:
> + not:
> + anyOf:
Thanks for the changes. This "anyOf" you can skip. It was needed in that
example because multiple properties should trigger restriction of maxItems.
In your case it is sufficient:
if:
not:
required:
- dma-requests
then:
....
Rest looks good.
> + - required:
> + - dma-requests
> +then:
> + properties:
> + interrupts:
> + maxItems: 8
Best regards,
Krzysztof
Powered by blists - more mailing lists