From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Frank Li <Frank.Li@nxp.com>,
vkoul@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
peng.fan@nxp.com, joy.zou@nxp.com, shenwei.wang@nxp.com,
imx@lists.linux.dev
Subject: Re: [PATCH v5 12/12] dt-bindings: fsl-dma: fsl-edma: add edma3 compatible string
Date: Tue, 13 Jun 2023 23:43:31 +0200 [thread overview]
Message-ID: <b3a25a5a-d39a-81bd-0593-7a4b76aeb9bf@linaro.org> (raw)
In-Reply-To: <20230613213149.2076358-13-Frank.Li@nxp.com>
On 13/06/2023 23:31, Frank Li wrote:
> Extend Freescale eDMA driver bindings to support eDMA3 IP blocks in
> i.MX8QM and i.MX8QXP SoCs. In i.MX93, both eDMA3 and eDMA4 are now.
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> .../devicetree/bindings/dma/fsl,edma.yaml | 118 +++++++++++++++---
> 1 file changed, 100 insertions(+), 18 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/dma/fsl,edma.yaml b/Documentation/devicetree/bindings/dma/fsl,edma.yaml
> index 5fd8fc604261..2f79492fb332 100644
> --- a/Documentation/devicetree/bindings/dma/fsl,edma.yaml
> +++ b/Documentation/devicetree/bindings/dma/fsl,edma.yaml
> @@ -21,32 +21,20 @@ properties:
> - enum:
> - fsl,vf610-edma
> - fsl,imx7ulp-edma
> + - fsl,imx8qm-adma
> + - fsl,imx8qm-edma
> + - fsl,imx93-edma3
> + - fsl,imx93-edma4
> - items:
> - const: fsl,ls1028a-edma
> - const: fsl,vf610-edma
>
> - reg:
> - minItems: 2
> - maxItems: 3
> -
> - interrupts:
> - minItems: 2
> - maxItems: 17
What is happening here?
> -
> - interrupt-names:
> - minItems: 2
> - maxItems: 17
> -
> - "#dma-cells":
> - const: 2
> -
> - dma-channels:
> - const: 32
No, why all these are being removed?
> -
> clocks:
> + minItems: 1
> maxItems: 2
>
> clock-names:
> + minItems: 1
> maxItems: 2
>
> big-endian:
> @@ -55,6 +43,43 @@ properties:
> eDMA are implemented in big endian mode, otherwise in little mode.
> type: boolean
>
> +if:
This should not be outside of your allOf. This patch looks entirely
different than your v4 and I don't really understand why.
> + properties:
> + compatible:
> + contains:
> + enum:
> + - fsl,imx8qm-adma
> + - fsl,imx8qm-edma
> + - fsl,imx93-edma3
> + - fsl,imx93-edma4
> +then:
> + properties:
> + reg:
> + maxItems: 1
> + interrupts:
> + minItems: 1
> + maxItems: 64
What's more, you don't have these properties defined in top-level.
Sorry, they should not be moved. I did not ask for this.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-13 21:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 21:31 [PATCH v5 00/12] dmaengine: edma: add freescale edma v3 support Frank Li
2023-06-13 21:31 ` [PATCH v5 01/12] dmaengine: fsl-edma: clean up EXPORT_SYMBOL_GPL in fsl-edma-common.c Frank Li
2023-06-13 21:31 ` [PATCH v5 02/12] dmaengine: fsl-edma: clean up fsl_edma_irq_exit() Frank Li
2023-06-13 21:31 ` [PATCH v5 03/12] dmaengine: fsl-edma: transition from bool fields to bitmask flags in drvdata Frank Li
2023-06-13 21:31 ` [PATCH v5 04/12] dmaengine: fsl-edma: Remove enum edma_version Frank Li
2023-06-13 21:31 ` [PATCH v5 05/12] dmaengine: fsl-edma: move common IRQ handler to common.c Frank Li
2023-06-13 21:31 ` [PATCH v5 06/12] dmaengine: fsl-edma: simply ATTR_DSIZE and ATTR_SSIZE by using ffs() Frank Li
2023-06-13 21:31 ` [PATCH v5 07/12] dmaengine: fsl-edma: refactor using devm_clk_get_enabled Frank Li
2023-06-13 21:31 ` [PATCH v5 08/12] dmaengine: fsl-edma: move clearing of register interrupt into setup_irq function Frank Li
2023-06-13 21:31 ` [PATCH v5 09/12] dmaengine: fsl-edma: refactor chan_name setup and safety Frank Li
2023-06-13 21:31 ` [PATCH v5 10/12] dmaengine: fsl-edma: move tcd into struct fsl_dma_chan Frank Li
2023-06-13 21:31 ` [PATCH v5 11/12] dmaengine: fsl-edma: integrate v3 support Frank Li
2023-06-13 21:31 ` [PATCH v5 12/12] dt-bindings: fsl-dma: fsl-edma: add edma3 compatible string Frank Li
2023-06-13 21:43 ` Krzysztof Kozlowski [this message]
2023-06-13 22:01 ` Frank Li
2023-06-14 6:39 ` Krzysztof Kozlowski
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=b3a25a5a-d39a-81bd-0593-7a4b76aeb9bf@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Frank.Li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=joy.zou@nxp.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=shenwei.wang@nxp.com \
--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