linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Cc: Marc Zyngier <maz@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
	Biwen Li <biwen.li@nxp.com>, Zhiqiang Hou <Zhiqiang.Hou@nxp.com>,
	Kurt Kanzenbach <kurt@linutronix.de>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: [RFC PATCH devicetree 03/10] dt-bindings: ls-extirq: replace "interrupt-map" documentation with "fsl,extirq-map"
Date: Tue, 14 Dec 2021 03:37:53 +0200	[thread overview]
Message-ID: <20211214013800.2703568-4-vladimir.oltean@nxp.com> (raw)
In-Reply-To: <20211214013800.2703568-1-vladimir.oltean@nxp.com>

This change does 3 things at once:
- documents the recently added "fsl,extirq-map" property, which replaces
  "interrupt-map"
- clarifies the format of the property whose name is changing
- hides the "interrupt-map" property, that the driver still supports for
  backwards compatibility reasons, although not for long.

Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
 .../bindings/interrupt-controller/fsl,ls-extirq.txt | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.txt b/Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.txt
index 4d47df1a5c91..cddf1aa032be 100644
--- a/Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.txt
+++ b/Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.txt
@@ -18,9 +18,13 @@ Required properties:
 - reg: Specifies the Interrupt Polarity Control Register (INTPCR) in
   the SCFG or the External Interrupt Control Register (IRQCR) in
   the ISC.
-- interrupt-map: Specifies the mapping from external interrupts to GIC
-  interrupts.
-- interrupt-map-mask: Must be <0xffffffff 0>.
+- fsl,extirq-map: An array of elements through which the mapping between
+  external interrupts and GIC interrupts is specified. The first member of each
+  array element is the index of the extirq line. The second member must be
+  zero. The third member must be a phandle to the interrupt parent (the GIC).
+  The remaining number of members in an array element depends on the
+  #interrupt-cells property of the interrupt parent, and are used to specify
+  the parent interrupt.
 
 Example:
 	scfg: scfg@1570000 {
@@ -37,14 +41,13 @@ Example:
 			#address-cells = <0>;
 			interrupt-controller;
 			reg = <0x1ac 4>;
-			interrupt-map =
+			fsl,extirq-map =
 				<0 0 &gic GIC_SPI 163 IRQ_TYPE_LEVEL_HIGH>,
 				<1 0 &gic GIC_SPI 164 IRQ_TYPE_LEVEL_HIGH>,
 				<2 0 &gic GIC_SPI 165 IRQ_TYPE_LEVEL_HIGH>,
 				<3 0 &gic GIC_SPI 167 IRQ_TYPE_LEVEL_HIGH>,
 				<4 0 &gic GIC_SPI 168 IRQ_TYPE_LEVEL_HIGH>,
 				<5 0 &gic GIC_SPI 169 IRQ_TYPE_LEVEL_HIGH>;
-			interrupt-map-mask = <0xffffffff 0x0>;
 		};
 	};
 
-- 
2.25.1


  parent reply	other threads:[~2021-12-14  1:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14  1:37 [RFC PATCH devicetree 00/10] Do something about ls-extirq interrupt-map breakage Vladimir Oltean
2021-12-14  1:37 ` [RFC PATCH devicetree 01/10] irqchip/ls-extirq: rename "interrupt-map" OF property to "fsl,extirq-map" Vladimir Oltean
2021-12-14  8:46   ` Kurt Kanzenbach
2021-12-14 15:07   ` Rob Herring
2021-12-14  1:37 ` [RFC PATCH devicetree 02/10] Revert "arm64: dts: freescale: Fix 'interrupt-map' parent address cells" Vladimir Oltean
2021-12-14  1:37 ` Vladimir Oltean [this message]
2021-12-14  1:37 ` [RFC PATCH devicetree 04/10] arm64: dts: ls1043a: rename the "interrupt-map" of the extirq node to "fsl,extirq-map" Vladimir Oltean
2021-12-14  1:37 ` [RFC PATCH devicetree 05/10] arm64: dts: ls1046a: " Vladimir Oltean
2021-12-14  1:37 ` [RFC PATCH devicetree 06/10] arm64: dts: ls1088a: " Vladimir Oltean
2021-12-14  1:37 ` [RFC PATCH devicetree 07/10] arm64: dts: ls208xa: " Vladimir Oltean
2021-12-14  1:37 ` [RFC PATCH devicetree 08/10] arm64: dts: lx2160a: " Vladimir Oltean
2021-12-14  1:37 ` [RFC PATCH devicetree 09/10] ARM: dts: ls1021a: " Vladimir Oltean
2021-12-14  1:38 ` [RFC PATCH devicetree 10/10] dt-bindings: ls-extirq: add a YAML schema for the validator Vladimir Oltean
2021-12-14 15:21   ` Rob Herring
2021-12-14  8:51 ` [RFC PATCH devicetree 00/10] Do something about ls-extirq interrupt-map breakage Marc Zyngier
2021-12-14  9:58   ` Vladimir Oltean
2021-12-14 10:20     ` Marc Zyngier
2021-12-14 10:30       ` Vladimir Oltean
2021-12-14 10:39         ` Marc Zyngier
2021-12-14 10:53           ` Vladimir Oltean
2021-12-14 11:11             ` Marc Zyngier
2022-03-24 17:10       ` Vladimir Oltean
2022-03-24 17:21         ` Marc Zyngier
2022-03-24 17:34           ` Vladimir Oltean
2022-03-24 18:06             ` Marc Zyngier
2022-03-24 19:09               ` Vladimir Oltean
2022-03-24 20:14                 ` Marc Zyngier
2022-03-25 10:34                 ` Robin Murphy
2022-03-25 17:54                   ` Vladimir Oltean

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=20211214013800.2703568-4-vladimir.oltean@nxp.com \
    --to=vladimir.oltean@nxp.com \
    --cc=Zhiqiang.Hou@nxp.com \
    --cc=biwen.li@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kurt@linutronix.de \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=maz@kernel.org \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).