From: Robin Murphy <robin.murphy@arm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
"Lad, Prabhakar" <prabhakar.csengg@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andre Przywara <andre.przywara@arm.com>,
Conor Dooley <conor.dooley@microchip.com>,
Samuel Holland <samuel@sholland.org>,
Biju Das <biju.das.jz@bp.renesas.com>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Atish Patra <atishp@atishpatra.org>,
"Lad, Prabhakar" <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Subject: Re: Similar SoCs with different CPUs and interrupt bindings
Date: Wed, 21 Sep 2022 11:27:14 +0100 [thread overview]
Message-ID: <146a749f-f4f0-c188-d6a3-1b41d88487ec@arm.com> (raw)
In-Reply-To: <b49de03c-2d88-ad81-7bdb-a33e6841481e@linaro.org>
On 2022-09-21 11:17, Krzysztof Kozlowski wrote:
> On 21/09/2022 12:14, Robin Murphy wrote:
>>> +#define SOC_PERIPHERAL_IRQ_NUMBER(na) (na + 32)
>>> +#define SOC_PERIPHERAL_IRQ(nr, na) GIC_SPI nr SOC_PERIPHERAL_IRQ_NUMBER(na)
>>> / {
>>> compatible = "renesas,r9a07g043";
>>> #address-cells = <2>;
>>> @@ -128,7 +130,7 @@ ssi1: ssi@1004a000 {
>>> compatible = "renesas,r9a07g043-ssi",
>>> "renesas,rz-ssi";
>>> reg = <0 0x1004a000 0 0x400>;
>>> - interrupts = <GIC_SPI 330 IRQ_TYPE_LEVEL_HIGH>,
>>> + interrupts = <SOC_PERIPHERAL_IRQ(330, IRQ_TYPE_LEVEL_HIGH)>,
>>>
>>>
>>>
>>> Or any other method like that....
>>
>> Which will generate the text:
>>
>> "interrupts = <GIC_SPI 330 (IRQ_TYPE_LEVEL_HIGH + 32)>,"
>>
>> (give or take some whitespace)
>>
>> CPP supports constant expressions in #if and #elif directives, but
>> macros are purely literal text replacement. It might technically be
>> achievable with some insane CPP metaprogramming, but for all practical
>> purposes this is a non-starter unless dtc itself grows the ability to
>> process arithmetic expressions.
>
> Except I put it into flags, not to IRQ number, it works, so I am not
> sure why do you call it non-starter?
Oh, it seems dtc *does* understand arithmetic already, that's what I was
missing.
$ echo "/dts-v1/;/{foo = <(2 + 3)>;};" | dtc -Odts
/dts-v1/;
/ {
foo = <0x05>;
};
Thanks for teaching me something new!
Robin.
next prev parent reply other threads:[~2022-09-21 10:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 7:46 Geert Uytterhoeven
2022-09-21 8:49 ` Krzysztof Kozlowski
2022-09-21 9:20 ` Lad, Prabhakar
2022-09-21 9:26 ` Krzysztof Kozlowski
2022-09-21 10:07 ` Lad, Prabhakar
2022-09-21 10:08 ` Geert Uytterhoeven
2022-09-21 10:10 ` Krzysztof Kozlowski
2022-09-21 21:05 ` Conor Dooley
2022-09-21 10:14 ` Robin Murphy
2022-09-21 10:17 ` Krzysztof Kozlowski
2022-09-21 10:27 ` Robin Murphy [this message]
2022-09-21 10:10 ` Geert Uytterhoeven
2022-09-21 9:20 ` Robin Murphy
2022-09-21 10:13 ` Geert Uytterhoeven
2022-09-21 10:20 ` Krzysztof Kozlowski
2022-09-22 6:30 ` Arnd Bergmann
2022-09-22 6:40 ` Geert Uytterhoeven
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=146a749f-f4f0-c188-d6a3-1b41d88487ec@arm.com \
--to=robin.murphy@arm.com \
--cc=Chris.Paterson2@renesas.com \
--cc=andre.przywara@arm.com \
--cc=arnd@arndb.de \
--cc=atishp@atishpatra.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=olof@lixom.net \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.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
all inboxes | Powered by JetHome®