One caveat is that the 'interrupts' property update _must_ go hand in hand with the newly added 'use-alternative-interrupt' property. Is there an easy way to avoid it? Signed-off-by: Eugeniu Rosca <erosca@xxxxxxxxxxxxxx> --- arch/arm64/boot/dts/renesas/ulcb.dtsi | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) diff --git a/arch/arm64/boot/dts/renesas/ulcb.dtsi b/arch/arm64/boot/dts/renesas/ulcb.dtsi index d2ba9598cd1e..168dadbd1185 100644 --- a/arch/arm64/boot/dts/renesas/ulcb.dtsi +++ b/arch/arm64/boot/dts/renesas/ulcb.dtsi @@ -174,6 +174,46 @@ &extalr_clk { clock-frequency = <32768>; }; +&gpio0 { + use-alternative-interrupt; + interrupts = <GIC_SPI 248 IRQ_TYPE_LEVEL_HIGH>; +}; + +&gpio1 { + use-alternative-interrupt; + interrupts = <GIC_SPI 249 IRQ_TYPE_LEVEL_HIGH>; +}; + +&gpio2 { + use-alternative-interrupt; + interrupts = <GIC_SPI 250 IRQ_TYPE_LEVEL_HIGH>; +}; + +&gpio3 { + use-alternative-interrupt; + interrupts = <GIC_SPI 251 IRQ_TYPE_LEVEL_HIGH>; +}; + +&gpio4 { + use-alternative-interrupt; + interrupts = <GIC_SPI 252 IRQ_TYPE_LEVEL_HIGH>; +}; + +&gpio5 { + use-alternative-interrupt; + interrupts = <GIC_SPI 253 IRQ_TYPE_LEVEL_HIGH>; +}; + +&gpio6 { + use-alternative-interrupt; + interrupts = <GIC_SPI 254 IRQ_TYPE_LEVEL_HIGH>; +}; + +&gpio7 { + use-alternative-interrupt; + interrupts = <GIC_SPI 255 IRQ_TYPE_LEVEL_HIGH>; +}; + &hdmi0 { status = "okay"; -- 2.26.0