From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <maz@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
bcm-kernel-feedback-list@broadcom.com (maintainer:BROADCOM
BCM281XX/BCM11XXX/BCM216XX ARM ARCHITE...),
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-arm-kernel@lists.infradead.org (moderated list:BROADCOM
BCM2835 ARM ARCHITECTURE),
Souvik Chakravarty <Souvik.Chakravarty@arm.com>,
Jim Quinlan <james.quinlan@broadcom.com>,
Sudeep Holla <Sudeep.Holla@arm.com>,
Thanu Rangarajan <Thanu.Rangarajan@arm.com>
Subject: [PATCH RFC 1/2] dt-bindings: Define interrupt type for SGI interrupts
Date: Tue, 22 Oct 2019 17:05:46 -0700 [thread overview]
Message-ID: <20191023000547.7831-2-f.fainelli@gmail.com> (raw)
In-Reply-To: <20191023000547.7831-1-f.fainelli@gmail.com>
In preparation for allowing drivers to use SGIs, define a new value for
the first ARM GIC interrupt controller cell to take a new value to
specifically designate a SGI interrupt.
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
---
.../devicetree/bindings/interrupt-controller/arm,gic.yaml | 2 +-
include/dt-bindings/interrupt-controller/arm-gic.h | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/interrupt-controller/arm,gic.yaml b/Documentation/devicetree/bindings/interrupt-controller/arm,gic.yaml
index 9a47820ef346..2d0bfcbe4933 100644
--- a/Documentation/devicetree/bindings/interrupt-controller/arm,gic.yaml
+++ b/Documentation/devicetree/bindings/interrupt-controller/arm,gic.yaml
@@ -58,7 +58,7 @@ properties:
const: 3
description: |
The 1st cell is the interrupt type; 0 for SPI interrupts, 1 for PPI
- interrupts.
+ interrupts and 2 for SGI interrupts.
The 2nd cell contains the interrupt number for the interrupt type.
SPI interrupts are in the range [0-987]. PPI interrupts are in the
diff --git a/include/dt-bindings/interrupt-controller/arm-gic.h b/include/dt-bindings/interrupt-controller/arm-gic.h
index 35b6f69b7db6..2dcc394b7b6b 100644
--- a/include/dt-bindings/interrupt-controller/arm-gic.h
+++ b/include/dt-bindings/interrupt-controller/arm-gic.h
@@ -12,6 +12,7 @@
#define GIC_SPI 0
#define GIC_PPI 1
+#define GIC_SGI 2
/*
* Interrupt specifier cell 2.
--
2.17.1
next prev parent reply other threads:[~2019-10-23 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 0:05 [PATCH RFC 0/2] irqchip/gic: Allow the use of SGI interrupts Florian Fainelli
2019-10-23 0:05 ` Florian Fainelli [this message]
2019-10-23 0:05 ` [PATCH RFC 2/2] " Florian Fainelli
2019-10-23 13:22 ` Marc Zyngier
2019-10-23 17:02 ` Florian Fainelli
2019-10-24 8:27 ` Marc Zyngier
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=20191023000547.7831-2-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=Souvik.Chakravarty@arm.com \
--cc=Sudeep.Holla@arm.com \
--cc=Thanu.Rangarajan@arm.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=james.quinlan@broadcom.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).