All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Murray <andrew.murray@arm.com>
To: Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>
Cc: devicetree@vger.kernel.org
Subject: [PATCH v1 1/7] PCI: dt: Add legacy PCI IRQ defines
Date: Mon,  4 Nov 2019 16:38:15 +0000	[thread overview]
Message-ID: <20191104163834.8932-2-andrew.murray@arm.com> (raw)
In-Reply-To: <20191104163834.8932-1-andrew.murray@arm.com>

PCI devices can trigger interrupts via 4 physical/virtual lines known
as INTA, INTB, INTC or INTD. Due to interrupt swizzling it is often
required to describe the interrupt mapping in the device tree. Let's
add a define for each type to improve device tree clarity.

Signed-off-by: Andrew Murray <andrew.murray@arm.com>
---
 include/dt-bindings/interrupt-controller/irq.h | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/include/dt-bindings/interrupt-controller/irq.h b/include/dt-bindings/interrupt-controller/irq.h
index 9e3d183e1381..f9063fd661cd 100644
--- a/include/dt-bindings/interrupt-controller/irq.h
+++ b/include/dt-bindings/interrupt-controller/irq.h
@@ -17,4 +17,12 @@
 #define IRQ_TYPE_LEVEL_HIGH	4
 #define IRQ_TYPE_LEVEL_LOW	8
 
+/* Legacy PCI IRQ lines */
+#define IRQ_INTA		1
+#define IRQ_INTB		2
+#define IRQ_INTC		3
+#define IRQ_INTD		4
+
+#define IRQ_INT_ALL		7
+
 #endif
-- 
2.21.0


  reply	other threads:[~2019-11-04 16:38 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 16:38 [PATCH v1 0/7] PCI: dt: Remove magic numbers for legacy PCI IRQ interrupts Andrew Murray
2019-11-04 16:38 ` Andrew Murray
2019-11-04 16:38 ` Andrew Murray
2019-11-04 16:38 ` Andrew Murray [this message]
2019-11-06 23:43   ` [PATCH v1 1/7] PCI: dt: Add legacy PCI IRQ defines Rob Herring
2019-11-04 16:38 ` [PATCH v1 2/7] arm64: dts: Use IRQ flags for legacy PCI IRQ interrupts Andrew Murray
2019-11-04 16:38   ` Andrew Murray
2019-11-04 16:38   ` Andrew Murray
2019-11-06 10:03   ` Liviu Dudau
2019-11-06 10:03     ` Liviu Dudau
2019-11-08 14:34   ` Heiko Stuebner
2019-11-08 14:34     ` Heiko Stuebner
2019-11-08 14:34     ` Heiko Stuebner
2019-11-09  6:03   ` Wei Xu
2019-11-09  6:03     ` Wei Xu
2019-11-09  6:03     ` Wei Xu
2019-11-04 16:38 ` [PATCH v1 3/7] arm: " Andrew Murray
2019-11-04 16:38   ` Andrew Murray
2019-11-05 15:06   ` Linus Walleij
2019-11-05 15:06     ` Linus Walleij
2019-11-05 17:20   ` Jesper Nilsson
2019-11-05 17:20     ` Jesper Nilsson
2019-11-04 16:38 ` [PATCH v1 4/7] xtensa: " Andrew Murray
2019-11-04 16:38 ` [PATCH v1 5/7] powerpc: dts: fsl: " Andrew Murray
2019-11-12 12:48   ` Michael Ellerman
2019-11-04 16:38 ` [PATCH v1 6/7] powerpc: dts: " Andrew Murray
2019-11-12 12:48   ` Michael Ellerman
2019-11-04 16:38 ` [PATCH v1 7/7] dt-bindings: PCI: " Andrew Murray
2019-11-04 16:38   ` Andrew Murray
2019-11-04 16:38   ` Andrew Murray
2019-11-04 16:38   ` Andrew Murray
     [not found]   ` <20191104163834.8932-8-andrew.murray-5wv7dgnIgG8@public.gmane.org>
2019-11-05 15:08     ` Linus Walleij
2019-11-05 15:08       ` Linus Walleij
2019-11-05 15:08       ` Linus Walleij
2019-11-05 15:16       ` Andrew Murray
2019-11-05 15:16         ` Andrew Murray
2019-11-05 15:16         ` Andrew Murray
2019-11-06 23:47         ` Rob Herring
2019-11-06 23:47           ` Rob Herring
2019-11-06 23:47           ` Rob Herring
2019-11-06 23:47   ` Rob Herring
2019-11-06 23:47     ` Rob Herring
2019-11-06 23:47     ` Rob Herring
2019-11-06 23:47     ` Rob Herring

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=20191104163834.8932-2-andrew.murray@arm.com \
    --to=andrew.murray@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.