Re: [RESEND PATCH] gpio: omap: Fix interrupt names

2014-09-23 Thread Linus Walleij
On Fri, Sep 5, 2014 at 9:52 PM, Nishanth Menon 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,

Re: [RESEND PATCH] gpio: omap: Fix interrupt names

2014-09-23 Thread Linus Walleij
On Fri, Sep 5, 2014 at 9:52 PM, Nishanth Menon n...@ti.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

Re: [RESEND PATCH] gpio: omap: Fix interrupt names

2014-09-19 Thread Alexandre Courbot
On Sat, Sep 6, 2014 at 4:52 AM, Nishanth Menon 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

Re: [RESEND PATCH] gpio: omap: Fix interrupt names

2014-09-19 Thread Alexandre Courbot
On Sat, Sep 6, 2014 at 4:52 AM, Nishanth Menon n...@ti.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

Re: [RESEND PATCH] gpio: omap: Fix interrupt names

2014-09-17 Thread Javier Martinez Canillas
Hello Linus, On Fri, Sep 5, 2014 at 9:52 PM, Nishanth Menon 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

Re: [RESEND PATCH] gpio: omap: Fix interrupt names

2014-09-17 Thread Javier Martinez Canillas
Hello Linus, On Fri, Sep 5, 2014 at 9:52 PM, Nishanth Menon n...@ti.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

[RESEND PATCH] gpio: omap: Fix interrupt names

2014-09-05 Thread Nishanth Menon
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

[RESEND PATCH] gpio: omap: Fix interrupt names

2014-09-05 Thread Nishanth Menon
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

Re: [PATCH] gpio: omap: Fix interrupt names

2014-08-22 Thread Kevin Hilman
Nishanth Menon writes: > 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,

Re: [PATCH] gpio: omap: Fix interrupt names

2014-08-22 Thread Kevin Hilman
Nishanth Menon n...@ti.com writes: 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.

Re: [PATCH] gpio: omap: Fix interrupt names

2014-08-21 Thread Javier Martinez Canillas
Hello, On Thu, Aug 21, 2014 at 3:37 PM, Santosh Shilimkar wrote: > On Thursday 21 August 2014 09:19 AM, Nishanth Menon 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

Re: [PATCH] gpio: omap: Fix interrupt names

2014-08-21 Thread Santosh Shilimkar
On Thursday 21 August 2014 09:19 AM, Nishanth Menon 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,

[PATCH] gpio: omap: Fix interrupt names

2014-08-21 Thread Nishanth Menon
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

[PATCH] gpio: omap: Fix interrupt names

2014-08-21 Thread Nishanth Menon
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

Re: [PATCH] gpio: omap: Fix interrupt names

2014-08-21 Thread Santosh Shilimkar
On Thursday 21 August 2014 09:19 AM, Nishanth Menon 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

Re: [PATCH] gpio: omap: Fix interrupt names

2014-08-21 Thread Javier Martinez Canillas
Hello, On Thu, Aug 21, 2014 at 3:37 PM, Santosh Shilimkar santosh.shilim...@ti.com wrote: On Thursday 21 August 2014 09:19 AM, Nishanth Menon 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