mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "irqchip-bot for Apurva Nandan" <tip-bot2@linutronix.de>
To: linux-kernel@vger.kernel.org
Cc: Apurva Nandan <a-nandan@ti.com>, Rob Herring <robh@kernel.org>,
	Marc Zyngier <maz@kernel.org>,
	tglx@linutronix.de
Subject: [irqchip: irq/irqchip-next] dt-bindings: interrupt-controller: ti,sci-intr: Fix missing reg property in the binding
Date: Thu, 29 Sep 2022 10:21:00 -0000	[thread overview]
Message-ID: <166444686053.401.11179384254910309532.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20220819190729.32358-4-a-nandan@ti.com>

The following commit has been merged into the irq/irqchip-next branch of irqchip:

Commit-ID:     daa0b6d0187599a574cb5cb392b259bda3dcf979
Gitweb:        https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms/daa0b6d0187599a574cb5cb392b259bda3dcf979
Author:        Apurva Nandan <a-nandan@ti.com>
AuthorDate:    Sat, 20 Aug 2022 00:37:29 +05:30
Committer:     Marc Zyngier <maz@kernel.org>
CommitterDate: Thu, 29 Sep 2022 11:13:43 +01:00

dt-bindings: interrupt-controller: ti,sci-intr: Fix missing reg property in the binding

Fix the following warning in dtbs_check
interrupt-controller@a00000: Unevaluated properties are not allowed ('reg' was unexpected)

Add the reg property in the schema.

Signed-off-by: Apurva Nandan <a-nandan@ti.com>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20220819190729.32358-4-a-nandan@ti.com
---
 Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.yaml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.yaml b/Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.yaml
index e12aee4..c99cc73 100644
--- a/Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.yaml
+++ b/Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.yaml
@@ -58,6 +58,9 @@ properties:
         1 = If intr supports edge triggered interrupts.
         4 = If intr supports level triggered interrupts.
 
+  reg:
+    maxItems: 1
+
   interrupt-controller: true
 
   '#interrupt-cells':

      parent reply	other threads:[~2022-09-29 10:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 19:07 [PATCH 0/3] Fix ti,sci-inta/intr and mmc dtbs_check warnings for TI K3 platforms Apurva Nandan
2022-08-19 19:07 ` [PATCH 1/3] dt-bindings: irqchip: ti,sci-inta: Fix warning '#interrupt-cells' was unexpected Apurva Nandan
2022-08-22 19:14   ` Rob Herring
2022-09-29 10:21   ` [irqchip: irq/irqchip-next] dt-bindings: irqchip: ti,sci-inta: Fix warning for missing #interrupt-cells irqchip-bot for Apurva Nandan
2022-08-19 19:07 ` [PATCH 2/3] dt-bindings: mmc: Fix 'dma-coherent' was unexpected Apurva Nandan
2022-08-22 19:16   ` Rob Herring
2022-08-26  9:16   ` Ulf Hansson
2022-08-19 19:07 ` [PATCH 3/3] dt-bindings: interrupt-controller: Fix 'reg' " Apurva Nandan
2022-08-22 19:16   ` Rob Herring
2022-09-29 10:21   ` irqchip-bot for Apurva Nandan [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=166444686053.401.11179384254910309532.tip-bot2@tip-bot2 \
    --to=tip-bot2@linutronix.de \
    --cc=a-nandan@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@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

all inboxes | Powered by JetHome®