From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bhargav Joshi <j.bhargav.u@gmail.com>
Cc: Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Peter Ujfalusi <peter.ujfalusi@gmail.com>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, goledhruva@gmail.com,
m-chawdhry@ti.com, daniel.baluta@gmail.com, simona.toaca@nxp.com
Subject: Re: [PATCH v2] dt-bindings: dma: ti,dma-crossbar: Convert to DT schema
Date: Mon, 13 Jul 2026 07:59:42 +0200 [thread overview]
Message-ID: <7444091d-c4bf-40d9-a163-806a64565ce9@kernel.org> (raw)
In-Reply-To: <CAOWyW_79oQB0L=3MtCnRuLst3=5ATJj=wpSS_550skTswUE2LQ@mail.gmail.com>
On 12/07/2026 18:28, Bhargav Joshi wrote:
> Hi,
>
> On Sun, Jul 12, 2026 at 6:22 PM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On Wed, Jul 08, 2026 at 10:02:18PM +0530, Bhargav Joshi wrote:
>>> +properties:
>>> + compatible:
>>> + enum:
>>> + - ti,dra7-dma-crossbar
>>> + - ti,am335x-edma-crossbar
>>> +
>>> + reg:
>>> + maxItems: 1
>>> +
>>> + "#dma-cells":
>>> + minimum: 1
>>> + maximum: 3
>>
>> That's rather:
>> enum: [1, 3]
>>
>> right?
> value 2 is required by DRA7 enhanced DMA crossbar (edma_xbar), and it is
> used in dra7-l4.dtsi so i think we can keep it unless you specifically
> prefer enum: [1, 2, 3]
I missed that edma device. It is fine.
>
>>
>>> +
>>> + dma-requests:
>>> + minimum: 1
>>> + maximum: 256
>>> +
>>> + dma-masters:
>>> + maxItems: 1
>>> +
>>> + ti,dma-safe-map:
>>> + $ref: /schemas/types.yaml#/definitions/uint32
>>> + description: Safe routing value for unused request lines
>>> +
>>> + ti,reserved-dma-request-ranges:
>>> + $ref: /schemas/types.yaml#/definitions/uint32-matrix
>>> + description:
>>> + DMA request ranges which should not be used when mapping xbar input to
>>> + DMA request, they are either allocated to be used by for example the DSP
>>> + or they are used as memcpy channels in eDMA.
>>> + items:
>>> + items:
>>> + - description: starting DMA request line number
>>> + - description: number of consecutive lines to reserve
>>> +
>>> +required:
>>> + - compatible
>>> + - reg
>>> + - "#dma-cells"
>>> + - dma-requests
>>> + - dma-masters
>>> +
>>> +allOf:
>>> + - $ref: dma-router.yaml#
>>> +
>>> + - if:
>>> + properties:
>>> + compatible:
>>> + contains:
>>> + const: ti,am335x-edma-crossbar
>>> + then:
>>> + properties:
>>> + "#dma-cells":
>>> + const: 3
>>
>> else:
>> properties:
>> dma-cels:
>> const: 1
> Yes but this should be rather,
> else:
> properties:
> '#dma-cells':
> enum: [1, 2]
> as dra7 doesn't use value 3 but uses 1 and 2, I will add it in next version
Yes
Best regards,
Krzysztof
prev parent reply other threads:[~2026-07-13 5:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 16:32 [PATCH v2] dt-bindings: dma: ti,dma-crossbar: Convert to DT schema Bhargav Joshi
2026-07-12 12:52 ` Krzysztof Kozlowski
2026-07-12 16:28 ` Bhargav Joshi
2026-07-13 5:59 ` Krzysztof Kozlowski [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=7444091d-c4bf-40d9-a163-806a64565ce9@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=goledhruva@gmail.com \
--cc=j.bhargav.u@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=peter.ujfalusi@gmail.com \
--cc=robh@kernel.org \
--cc=simona.toaca@nxp.com \
--cc=vigneshr@ti.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