From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: shawnguo@kernel.org, linux-arm-kernel@lists.infradead.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
imx@lists.linux.dev, Fabio Estevam <festevam@denx.de>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH 1/2] dt-bindings: soc: imx: fsl, imx-anatop: Fix the i.MX7 irq number
Date: Fri, 25 Oct 2024 12:19:07 +0200 [thread overview]
Message-ID: <5991537.MhkbZ0Pkbq@steina-w> (raw)
In-Reply-To: <20241025004159.1571782-1-festevam@gmail.com>
Hi Fabio,
thanks for the patch.
Am Freitag, 25. Oktober 2024, 02:41:58 CEST schrieb Fabio Estevam:
> From: Fabio Estevam <festevam@denx.de>
>
> Unlike the other i.MX devices, i.MX7 has only two anatop interrupts.
>
> Add logic that contemplates such case to fix the following
> dt-schema warning:
>
> anatop@30360000: interrupts: [[0, 49, 4], [0, 51, 4]] is too short
>
> Signed-off-by: Fabio Estevam <festevam@denx.de>
Reviewed-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> ---
> .../bindings/soc/imx/fsl,imx-anatop.yaml | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/soc/imx/fsl,imx-anatop.yaml b/Documentation/devicetree/bindings/soc/imx/fsl,imx-anatop.yaml
> index c4ae4f28422b..ae708a658d52 100644
> --- a/Documentation/devicetree/bindings/soc/imx/fsl,imx-anatop.yaml
> +++ b/Documentation/devicetree/bindings/soc/imx/fsl,imx-anatop.yaml
> @@ -36,6 +36,7 @@ properties:
> - description: Temperature sensor event
> - description: Brown-out event on either of the support regulators
> - description: Brown-out event on either the core, gpu or soc regulators
> + minItems: 2
>
> tempmon:
> type: object
> @@ -52,6 +53,23 @@ required:
> - compatible
> - reg
>
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - fsl,imx7d-anatop
> + then:
> + properties:
> + interrupts:
> + maxItems: 2
> + else:
> + properties:
> + interrupts:
> + minItems: 3
> + maxItems: 3
> +
> additionalProperties: false
>
> examples:
>
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2024-10-25 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 0:41 [PATCH 1/2] dt-bindings: soc: imx: fsl,imx-anatop: Fix the i.MX7 irq number Fabio Estevam
2024-10-25 0:41 ` [PATCH 2/2] dt-bindings: soc: imx: fsl,imx-anatop: Add additional regulators Fabio Estevam
2024-10-25 10:14 ` [PATCH 2/2] dt-bindings: soc: imx: fsl, imx-anatop: " Alexander Stein
2024-10-27 21:45 ` [PATCH 2/2] dt-bindings: soc: imx: fsl,imx-anatop: " Rob Herring
2024-10-25 10:19 ` Alexander Stein [this message]
2024-10-27 21:43 ` [PATCH 1/2] dt-bindings: soc: imx: fsl,imx-anatop: Fix the i.MX7 irq number Rob Herring (Arm)
2024-11-02 3:21 ` Shawn Guo
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=5991537.MhkbZ0Pkbq@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh@kernel.org \
--cc=shawnguo@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