| 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: Fri, 19 Sep 2014 16:27:12 +0900 From: Alexandre Courbot <gnurou@...il.com> To: Nishanth Menon <nm@...com> Cc: Linus Walleij <linus.walleij@...aro.org>, Kevin Hilman <khilman@...prootsystems.com>, Santosh Shilimkar <santosh.shilimkar@...com>, Javier Martinez Canillas <javier@...hile0.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>, linux-omap@...r.kernel.org Subject: Re: [RESEND PATCH] gpio: omap: Fix interrupt names On Sat, Sep 6, 2014 at 4:52 AM, Nishanth Menon <nm@...com> wrote: > When viewing the /proc/interrupts, there is no information about which > GPIO bank a specific gpio interrupt is hooked on to. This is more than a > bit irritating as such information can esily be provided back to the > user and at times, can be crucial for debug. > > So, instead of displaying something like: > 31: 0 0 GPIO 0 palmas > 32: 0 0 GPIO 27 mmc0 > > Display the following with appropriate device name: > 31: 0 0 4ae10000.gpio 0 palmas > 32: 0 0 4805d000.gpio 27 mmc0 > > This requires that we create irq_chip instance specific for each GPIO > bank which is trivial to achieve. Acked-by: Alexandre Courbot <acourbot@...dia.com> -- 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