linux-kernel - Re: [PATCH v4 8/8] ARM: dts: r9a06g032: Add support for GPIO interrupts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20251015114126.4df207b1@bootlin.com>
Date: Wed, 15 Oct 2025 11:41:26 +0200
From: Herve Codina <herve.codina@...tlin.com>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Hoan Tran
 <hoan@...amperecomputing.com>, Linus Walleij <linus.walleij@...aro.org>,
 Bartosz Golaszewski <brgl@...ev.pl>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Geert Uytterhoeven <geert+renesas@...der.be>, Magnus
 Damm <magnus.damm@...il.com>, Saravana Kannan <saravanak@...gle.com>, Serge
 Semin <fancer.lancer@...il.com>, Phil Edworthy <phil.edworthy@...esas.com>,
 linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-renesas-soc@...r.kernel.org, Pascal
 Eberhard <pascal.eberhard@...com>, Miquel Raynal
 <miquel.raynal@...tlin.com>, Thomas Petazzoni
 <thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH v4 8/8] ARM: dts: r9a06g032: Add support for GPIO
 interrupts

Hi Wolfram,

On Wed, 24 Sep 2025 23:48:40 +0200
Wolfram Sang <wsa+renesas@...g-engineering.com> wrote:

> > +			/*
> > +			 * interrupt-map has to be updated according to GPIO
> > +			 * usage. The src irq (0 field) has to be updated with
> > +			 * the needed GPIO interrupt number.
> > +			 * More items can be added (up to 8). Those items must
> > +			 * define one GIC interrupt line among 103 to 110.
> > +			 */
> > +			interrupt-map = <0 &gic GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH>;  
> 
> Okay, so my main concern here was that we setup some "random" default
> mapping for each board. Which is not true because this node is disabled
> by default. So, maybe we could rephrase the paragraph like
> 
> /*
>  * Example mapping entry. Board DTs need to overwrite 'interrupt-map'
>  * with their specific mapping. Check the irqmux binding documentation
>  * for details.
>  */

Will be updated in next iteration.

> 
> ? I will see if I can provide a useful board addition for the DB400
> boards...
> 

Best regards,
Hervé