From: Chris Morgan <macroalpha82@gmail.com>
To: linux-sunxi@lists.linux.dev
Cc: devicetree@vger.kernel.org, mripard@kernel.org,
samuel@sholland.org, jernej.skrabec@gmail.com, wens@csie.org,
conor+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
robh@kernel.org, ryan@testtoast.com,
Chris Morgan <macromorgan@hotmail.com>
Subject: [PATCH 1/2] dt-bindings: irq: sun7i-nmi: Add binding for the H616 NMI controller
Date: Sun, 14 Apr 2024 12:04:23 -0500 [thread overview]
Message-ID: <20240414170424.614921-2-macroalpha82@gmail.com> (raw)
In-Reply-To: <20240414170424.614921-1-macroalpha82@gmail.com>
From: Chris Morgan <macromorgan@hotmail.com>
Add binding for the H616 NMI controller. This is necessary to handle
interrupts from devices such as the internal PMIC.
Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
---
.../interrupt-controller/allwinner,sun7i-a20-sc-nmi.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/interrupt-controller/allwinner,sun7i-a20-sc-nmi.yaml b/Documentation/devicetree/bindings/interrupt-controller/allwinner,sun7i-a20-sc-nmi.yaml
index 83603180d8d9..4fc8b0320a31 100644
--- a/Documentation/devicetree/bindings/interrupt-controller/allwinner,sun7i-a20-sc-nmi.yaml
+++ b/Documentation/devicetree/bindings/interrupt-controller/allwinner,sun7i-a20-sc-nmi.yaml
@@ -32,6 +32,9 @@ properties:
- items:
- const: allwinner,sun50i-a100-nmi
- const: allwinner,sun9i-a80-nmi
+ - items:
+ - const: allwinner,sun50i-h616-nmi
+ - const: allwinner,sun9i-a80-nmi
reg:
maxItems: 1
--
2.34.1
next prev parent reply other threads:[~2024-04-14 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 17:04 [PATCH 0/2] Allwinner H616 NMI Controller Chris Morgan
2024-04-14 17:04 ` Chris Morgan [this message]
2024-04-14 22:40 ` [PATCH 1/2] dt-bindings: irq: sun7i-nmi: Add binding for the H616 NMI controller Andre Przywara
2024-04-14 17:04 ` [PATCH 2/2] arm64: dts: allwinner: h616: Add NMI device node Chris Morgan
2024-04-14 23:37 ` Andre Przywara
2024-04-18 15:59 ` Chris Morgan
2024-04-18 16:19 ` Andre Przywara
2024-04-18 17:52 ` Chris Morgan
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=20240414170424.614921-2-macroalpha82@gmail.com \
--to=macroalpha82@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=macromorgan@hotmail.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=ryan@testtoast.com \
--cc=samuel@sholland.org \
--cc=wens@csie.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