From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
vkoul@kernel.org, dmaengine@vger.kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, joy.zou@nxp.com,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH V3] dt-bindings: dma: fsl-edma: Convert to DT schema
Date: Sun, 29 May 2022 16:17:51 +0200 [thread overview]
Message-ID: <bdbf2fa9-214e-e9f3-5389-87864104e07d@linaro.org> (raw)
In-Reply-To: <20220527020507.392765-1-peng.fan@oss.nxp.com>
On 27/05/2022 04:05, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Convert the eDMA controller binding to DT schema.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
>
> V3:
> Address Krzysztof's comments, for reg/interrupts/clock-names
>
> V2:
> Typo fix
> Correct interrupts/interrupt-names/AllOf
>
>
> .../devicetree/bindings/dma/fsl,edma.yaml | 155 ++++++++++++++++++
> .../devicetree/bindings/dma/fsl-edma.txt | 111 -------------
> arch/arm64/boot/dts/freescale/imx93.dtsi | 2 +-
> 3 files changed, 156 insertions(+), 112 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/dma/fsl,edma.yaml
> delete mode 100644 Documentation/devicetree/bindings/dma/fsl-edma.txt
>
> diff --git a/Documentation/devicetree/bindings/dma/fsl,edma.yaml b/Documentation/devicetree/bindings/dma/fsl,edma.yaml
> new file mode 100644
> index 000000000000..050e6cd57727
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/dma/fsl,edma.yaml
> @@ -0,0 +1,155 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/dma/fsl,edma.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Freescale enhanced Direct Memory Access(eDMA) Controller
> +
> +description: |
> + The eDMA channels have multiplex capability by programmable
> + memory-mapped registers. channels are split into two groups, called
> + DMAMUX0 and DMAMUX1, specific DMA request source can only be multiplexed
> + by any channel of certain group, DMAMUX0 or DMAMUX1, but not both.
> +
> +maintainers:
> + - Peng Fan <peng.fan@nxp.com>
> +
> +properties:
> + compatible:
> + oneOf:
> + - enum:
> + - fsl,vf610-edma
> + - fsl,imx7ulp-edma
> + - items:
> + - const: fsl,ls1028a-edma
> + - const: fsl,vf610-edma
> +
> + reg:
> + minItems: 2
> + maxItems: 3
> +
> + interrupts:
> + minItems: 2
> + maxItems: 17
> +
> + interrupt-names:
> + minItems: 2
> + maxItems: 17
> +
> + "#dma-cells":
> + const: 2
> +
> + dma-channels:
> + const: 32
> +
> + clocks:
> + maxItems: 2
> +
> + clock-names:
> + maxItems: 2
> +
> + big-endian:
> + description: |
> + If present registers and hardware scatter/gather descriptors of the
> + eDMA are implemented in big endian mode, otherwise in little mode.
> + type: boolean
> +
> +required:
> + - "#dma-cells"
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> + - dma-channels
> +
> +allOf:
> + - $ref: "dma-controller.yaml#"
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: fsl,vf610-edma
> + then:
> + properties:
> + clock-names:
> + items:
> + - const: dmamux0
> + - const: dmamux1
> + interrupts:
> + maxItems: 2
> + interrupt-names:
> + items:
> + - const: edma-tx
> + - const: edma-err
> + reg:
> + maxItems: 3
> +
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: fsl,imx7ulp-edma
> + then:
> + properties:
> + clock-names:
> + items:
> + - const: dma
> + - const: dmamux0
> + interrupts:
> + maxItems: 17
Looks good, although the information about order of interrupts is lost
during conversion. The original bindings had:
"total 16 channel interrupt and 1 error interrupt(located in the last)"
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-05-29 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 2:05 [PATCH V3] dt-bindings: dma: fsl-edma: Convert to DT schema Peng Fan (OSS)
2022-05-29 14:17 ` Krzysztof Kozlowski [this message]
2022-06-10 13:50 ` Vinod Koul
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=bdbf2fa9-214e-e9f3-5389-87864104e07d@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=joy.zou@nxp.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh+dt@kernel.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).