From: Frank Li <Frank.li@nxp.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: 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 v6 12/12] dt-bindings: fsl-dma: fsl-edma: add edma3 compatible string
Date: Thu, 15 Jun 2023 10:37:04 -0400 [thread overview]
Message-ID: <ZIsiEIhmpS7DSs6R@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <0cddd5e8-3de1-1b6a-b4b8-6304e4c674cf@linaro.org>
On Thu, Jun 15, 2023 at 12:52:18PM +0200, Krzysztof Kozlowski wrote:
> On 14/06/2023 21:35, Frank Li wrote:
> > + # It is not necessary to write the interrupt name for each channel.
> > + # instead, you can simply maintain the sequential IRQ numbers as
> > + # defined for the DMA channels.
> > + interrupt-names: false
> > + clock-names:
>
> items:
> - const: dma
>
> clocks:
> maxItems: 1
>
> You do not allow more than one clock, right?
Yes, at least now. Only 1 clock needed.
>
> > + const: dma
> > + else:
>
> You already have two ifs, so you should not have else here, but rather
> make each if clause proper for your setup.
>
> BTW, the amount of differences point to very complicated schema, so you
> should think whether it makes sense to keep binding growing in the first
> place.
Any good ways if don't growing binding at the first place?
>
> > + properties:
> > + reg:
> > + minItems: 2
> > + maxItems: 3
> > + interrupts:
> > + minItems: 2
> > + maxItems: 17
>
> missing clocks restriction to minItems: 2
>
>
> > + "#dma-cells":
> > + const: 2
> > + dma-channels:
> > + const: 32
> > +
>
>
>
> Best regards,
> Krzysztof
>
prev parent reply other threads:[~2023-06-15 14:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 19:35 [PATCH v6 00/12] dmaengine: edma: add freescale edma v3 support Frank Li
2023-06-14 19:35 ` [PATCH v6 01/12] dmaengine: fsl-edma: clean up EXPORT_SYMBOL_GPL in fsl-edma-common.c Frank Li
2023-06-14 19:35 ` [PATCH v6 02/12] dmaengine: fsl-edma: clean up fsl_edma_irq_exit() Frank Li
2023-06-14 19:35 ` [PATCH v6 03/12] dmaengine: fsl-edma: transition from bool fields to bitmask flags in drvdata Frank Li
2023-06-14 19:35 ` [PATCH v6 04/12] dmaengine: fsl-edma: Remove enum edma_version Frank Li
2023-06-14 19:35 ` [PATCH v6 05/12] dmaengine: fsl-edma: move common IRQ handler to common.c Frank Li
2023-06-14 19:35 ` [PATCH v6 06/12] dmaengine: fsl-edma: simply ATTR_DSIZE and ATTR_SSIZE by using ffs() Frank Li
2023-06-14 19:35 ` [PATCH v6 07/12] dmaengine: fsl-edma: refactor using devm_clk_get_enabled Frank Li
2023-06-14 19:35 ` [PATCH v6 08/12] dmaengine: fsl-edma: move clearing of register interrupt into setup_irq function Frank Li
2023-06-14 19:35 ` [PATCH v6 09/12] dmaengine: fsl-edma: refactor chan_name setup and safety Frank Li
2023-06-14 19:35 ` [PATCH v6 10/12] dmaengine: fsl-edma: move tcd into struct fsl_dma_chan Frank Li
2023-06-14 19:35 ` [PATCH v6 11/12] dmaengine: fsl-edma: integrate v3 support Frank Li
2023-06-14 19:35 ` [PATCH v6 12/12] dt-bindings: fsl-dma: fsl-edma: add edma3 compatible string Frank Li
2023-06-15 10:52 ` Krzysztof Kozlowski
2023-06-15 14:37 ` Frank Li [this message]
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=ZIsiEIhmpS7DSs6R@lizhi-Precision-Tower-5810 \
--to=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=krzysztof.kozlowski@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