[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bb3b61b6-4f39-4123-be50-0e2c8f07eb99@linaro.org>
Date: Thu, 29 Feb 2024 10:49:43 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Frank Li <Frank.Li@....com>, Vinod Koul <vkoul@...nel.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, Peng Fan <peng.fan@....com>
Cc: imx@...ts.linux.dev, dmaengine@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
Joy Zou <joy.zou@....com>
Subject: Re: [PATCH 4/5] dt-bindings: fsl-dma: fsl-edma: add fsl,imx8ulp-edma
compatible string
On 27/02/2024 18:21, Frank Li wrote:
>
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: fsl,imx8ulp-edma
> + then:
> + properties:
> + clock:
> + maxItems: 33
> + clock-names:
> + items:
> + - const: dma
> + - pattern: "^CH[0-31]-clk$"
> + interrupt-names: false
> + interrupts:
> + maxItems: 32
> + "#dma-cells":
> + const: 3
Why suddenly fsl,vf610-edma can have from 2 to 33 clocks? Constrain
properly the variants.
Best regards,
Krzysztof
Powered by blists - more mailing lists