From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andrew Jeffery <andrew@codeconstruct.com.au>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH 2/2] dt-bindings: misc: aspeed,ast2400-cvic: Convert to DT schema
Date: Tue, 6 Aug 2024 08:12:12 +0200 [thread overview]
Message-ID: <ec19fe07-84bd-4c32-a886-e6126af52f4c@kernel.org> (raw)
In-Reply-To: <20240802-dt-warnings-irq-aspeed-dt-schema-v1-2-8cd4266d2094@codeconstruct.com.au>
On 02/08/2024 07:36, Andrew Jeffery wrote:
> Address warnings such as:
>
> +description:
> + The Aspeed AST2400 and AST2500 SoCs have a controller that provides interrupts
> + to the ColdFire coprocessor. It's not a normal interrupt controller and it
> + would be rather inconvenient to create an interrupt tree for it, as it
> + somewhat shares some of the same sources as the main ARM interrupt controller
> + but with different numbers.
> +
> + The AST2500 also supports a software generated interrupt.
> +
> +properties:
> + compatible:
> + items:
> + - enum:
> + - aspeed,ast2400-cvic
> + - aspeed,ast2500-cvic
> + - const: aspeed,cvic
> +
> + reg:
> + maxItems: 1
> +
> + valid-sources:
> + $ref: /schemas/types.yaml#/definitions/uint32-array
> + description:
> + One cell, bitmap of support sources for the implementation.
maxItems: 1
(and drop "One cell" - no need to repeat constraints in free form text)
BTW, for both bindings, I do not see any user in the kernel. Why is this
property needed in the DTS?
> +
> + copro-sw-interrupts:
> + $ref: /schemas/types.yaml#/definitions/uint32-array
uint32? I do not see anywhere usage as an array. The in-kernel driver
explicitly reads just uint32.
Anyway, if this is supposed to stay as array, then min/maxItems.
> + description:
> + A list of interrupt numbers that can be used as software interrupts from
> + the ARM to the coprocessor.
> +
> +required:
> + - compatible
> + - reg
> + - valid-sources> +
> +allOf:
> + - $ref: /schemas/interrupt-controller.yaml#
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-06 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 5:36 [PATCH 0/2] dt-bindings: interrupt-controller: Convert Aspeed (C)VIC to DT schema Andrew Jeffery
2024-08-02 5:36 ` [PATCH 1/2] dt-bindings: interrupt-controller: aspeed,ast2400-vic: Convert " Andrew Jeffery
2024-08-06 6:07 ` Krzysztof Kozlowski
2024-08-08 2:02 ` Andrew Jeffery
2024-08-02 5:36 ` [PATCH 2/2] dt-bindings: misc: aspeed,ast2400-cvic: " Andrew Jeffery
2024-08-06 6:12 ` Krzysztof Kozlowski [this message]
2024-08-08 2:06 ` Andrew Jeffery
2024-08-08 3:52 ` Andrew Jeffery
2024-08-06 17:29 ` Rob Herring
2024-08-08 2:07 ` Andrew Jeffery
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=ec19fe07-84bd-4c32-a886-e6126af52f4c@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/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