linux-kernel - RE: [PATCH net-next 1/2] net: renesas: rswitch: use per-port irq handlers

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 for Android: free password hash cracker in your pocket

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

Message-ID:
 <TYCPR01MB1104022CD76BDE941D1C22536D8072@TYCPR01MB11040.jpnprd01.prod.outlook.com>
Date: Fri, 20 Dec 2024 09:11:04 +0000
From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>
To: nikita.yoush <nikita.yoush@...entembedded.com>, Geert Uytterhoeven
	<geert@...ux-m68k.org>
CC: Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller"
	<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski
	<kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Geert Uytterhoeven
	<geert+renesas@...der.be>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"linux-renesas-soc@...r.kernel.org" <linux-renesas-soc@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Michael Dege
	<michael.dege@...esas.com>, Christian Mardmoeller
	<christian.mardmoeller@...esas.com>, Dennis Ostermann
	<dennis.ostermann@...esas.com>, "open list:OPEN FIRMWARE AND FLATTENED DEVICE
 TREE BINDINGS" <devicetree@...r.kernel.org>
Subject: RE: [PATCH net-next 1/2] net: renesas: rswitch: use per-port irq
 handlers

Hello Nikita-san,

> From: Nikita Yushchenko, Sent: Friday, December 20, 2024 5:09 PM
> 
> >> But it is not required to use the same interrupt for all ports - GWCA
> >> provides 8 data interrupts and allows arbitrary per-queue assignment
> >> of those. Support that by reading interrupt index for each port from
> >> optional 'irq-index' device tree property.
> >
> > Sorry, but I can't find where this property is documented?
> 
> I will add this.

Device tree properties should be a hardware description. However,
about the "irq-index", it seems a software configuration. So, even if we would
like to submit such a patch to add the property, it will be rejected.

Also, even if we can add a new device tree property, we should keep backward compatible.
However, this patch seems to break a backward compatibility.

Unfortunately, I don't have alternative solutions how to configurate per-port irq though...
# Maybe configfs??

Best regards,
Yoshihiro Shimoda

> Nikita