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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 23 Sep 2021 16:44:57 +0200 From: Andrew Lunn <andrew@...n.ch> To: Asmaa Mnebhi <asmaa@...dia.com> Cc: "andy.shevchenko@...il.com" <andy.shevchenko@...il.com>, "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>, "kuba@...nel.org" <kuba@...nel.org>, "linus.walleij@...aro.org" <linus.walleij@...aro.org>, "bgolaszewski@...libre.com" <bgolaszewski@...libre.com>, "davem@...emloft.net" <davem@...emloft.net>, "rjw@...ysocki.net" <rjw@...ysocki.net>, David Thompson <davthompson@...dia.com> Subject: Re: [PATCH v2 1/2] gpio: mlxbf2: Introduce IRQ support > No we don't. I double checked with the HW team and they confirmed that > YU_GPIO_CAUSE_FALL_EN and YU_GPIO_CAUSE_RISE_EN are used in > Both level and edge interrupts cases. How? They are different things. I suggest you test this. Make sure a level interrupt real does fire on level. One simple test is use a resistor to force the interrupt pin low. Your machine should then die in an interrupt storm, until the kernel declares the interrupt broken and disables it. Andrew
Powered by blists - more mailing lists