From: Kurt Kanzenbach <kurt@linutronix.de>
To: Vladimir Oltean <vladimir.oltean@nxp.com>,
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>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [RFC PATCH devicetree 01/10] irqchip/ls-extirq: rename "interrupt-map" OF property to "fsl,extirq-map"
Date: Tue, 14 Dec 2021 09:46:50 +0100 [thread overview]
Message-ID: <87wnk7375x.fsf@kurt> (raw)
In-Reply-To: <20211214013800.2703568-2-vladimir.oltean@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
On Tue Dec 14 2021, Vladimir Oltean wrote:
> This OF property was supposed to be named "fsl,extirq-map" since the
> first patch submissions, but at Rob Herring's suggestion it was named
> "interrupt-map":
> https://lore.kernel.org/lkml/20190927161118.GA19333@bogus/
nit: The preferred form is https://lore.kernel.org/r/<message-id>
[snip]
> diff --git a/drivers/irqchip/irq-ls-extirq.c b/drivers/irqchip/irq-ls-extirq.c
> index 853b3972dbe7..b6ecc5e3472f 100644
> --- a/drivers/irqchip/irq-ls-extirq.c
> +++ b/drivers/irqchip/irq-ls-extirq.c
> @@ -101,9 +101,15 @@ ls_extirq_parse_map(struct ls_extirq_data *priv, struct device_node *node)
> u32 mapsize;
> int ret;
>
> - map = of_get_property(node, "interrupt-map", &mapsize);
> - if (!map)
> - return -ENOENT;
> + map = of_get_property(node, "fsl,extirq-map", &mapsize);
> + if (!map) {
> + map = of_get_property(node, "interrupt-map", &mapsize);
> + if (!map)
> + return -ENOENT;
> +
> + pr_warn("\"interrupt-map\" is a reserved OF property, and support for it will be removed. Please use \"fsl,extirq-map\" instead.\n");
> + }
Looks reasonable. For instance, DSA does the same thing wrt "ports"
vs. "ethernet-ports".
Thanks,
Kurt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2021-12-14 8:46 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 [this message]
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 ` [RFC PATCH devicetree 03/10] dt-bindings: ls-extirq: replace "interrupt-map" documentation with "fsl,extirq-map" Vladimir Oltean
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=87wnk7375x.fsf@kurt \
--to=kurt@linutronix.de \
--cc=Zhiqiang.Hou@nxp.com \
--cc=biwen.li@nxp.com \
--cc=devicetree@vger.kernel.org \
--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 \
--cc=vladimir.oltean@nxp.com \
/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).