Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Frank Li <Frank.Li@nxp.com>, Vinod Koul <vkoul@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"open list:DMA GENERIC OFFLOAD ENGINE SUBSYSTEM"
	<dmaengine@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Cc: imx@lists.linux.dev
Subject: Re: [PATCH 1/1] dt-bindings: fsl-qdma: Convert to yaml format
Date: Tue, 21 May 2024 10:26:48 +0200	[thread overview]
Message-ID: <8a0e5863-27f7-47e4-9325-a686d5adffec@kernel.org> (raw)
In-Reply-To: <20240520203907.749347-1-Frank.Li@nxp.com>

On 20/05/2024 22:39, Frank Li wrote:
> Convert binding doc from txt to yaml.
> 
> Re-order interrupt-names to align example.


> +properties:
> +  compatible:
> +    enum:
> +      - fsl,ls1021a-qdma
> +      - fsl,ls1028a-qdma
> +      - fsl,ls1043a-qdma
> +      - fsl,ls1046a-qdma
> +
> +  reg:
> +    items:
> +      - description: Controller regs
> +      - description: Status regs
> +      - description: Block regs
> +
> +  interrupts:
> +    minItems: 2
> +    maxItems: 5
> +
> +  interrupt-names:
> +    minItems: 2
> +    items:
> +      - const: qdma-error
> +      - const: qdma-queue0
> +      - const: qdma-queue1
> +      - const: qdma-queue2
> +      - const: qdma-queue3
> +
> +  dma-channels:
> +    minItems: 1
> +    maxItems: 64

That's not a list. Did you just copy buggy fsl-edma?

> +
> +  fsl,dma-queues:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    description: Should contain number of queues supported.

Constraints?

> +
> +  block-number:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    description: the virtual block number
> +
> +  block-offset:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    description: the offset of different virtual block
> +
> +  status-sizes:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    description: status queue size of per virtual block
> +
> +  queue-sizes:
> +    $ref: /schemas/types.yaml#/definitions/uint32-array
> +    description:
> +      command queue size of per virtual block, the size number
> +      based on queues
> +
> +  big-endian:
> +    $ref: /schemas/types.yaml#/definitions/flag
> +    description:
> +      If present registers and hardware scatter/gather descriptors
> +      of the qDMA are implemented in big endian mode, otherwise in little
> +      mode.
> +
> +required:
> +  - compatible
> +  - reg
> +  - interrupts
> +  - interrupt-names
> +  - fsl,dma-queues
> +  - block-number
> +  - block-offset
> +  - status-sizes
> +  - queue-sizes
> +
> +unevaluatedProperties: false
> +
> +allOf:
> +  - $ref: dma-controller.yaml#

This goes above unevaluatedProperties.

Please constrain interrupts per variant.


Best regards,
Krzysztof


      reply	other threads:[~2024-05-21  8:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-20 20:39 [PATCH 1/1] dt-bindings: fsl-qdma: Convert to yaml format Frank Li
2024-05-21  8:26 ` 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=8a0e5863-27f7-47e4-9325-a686d5adffec@kernel.org \
    --to=krzk@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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