| 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
| ||
|
Message-ID: <CACRpkdZNOjty9=nigA+SKk3yC5vVjohwjd2Kg+KWV2EYixJ+ag@mail.gmail.com> Date: Fri, 6 Mar 2015 12:21:50 +0100 From: Linus Walleij <linus.walleij@...aro.org> To: Mika Westerberg <mika.westerberg@...ux.intel.com> Cc: Heikki Krogerus <heikki.krogerus@...ux.intel.com>, Mathias Nyman <mathias.nyman@...ux.intel.com>, Hans Holmberg <hans.holmberg@...el.com>, Benjamin Adler <benadler@....net>, "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 2/4] pinctrl: baytrail: Clear interrupt triggering from pins that are in GPIO mode On Mon, Feb 23, 2015 at 1:53 PM, Mika Westerberg <mika.westerberg@...ux.intel.com> wrote: > If the pin is already configured as GPIO and it has any of the triggering > flags set, we may get spurious interrupts depending on the state of the > pin. > > Prevent this by clearing the triggering flags on such pins. However, if the > pin is also configured as "direct IRQ" we leave the flags as is. Otherwise > it will prevent interrupts that are routed directly to IO-APIC. > > Signed-off-by: Mika Westerberg <mika.westerberg@...ux.intel.com> Patch applied for fixes. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists