summaryrefslogtreecommitdiff
path: root/drivers/gpio/gpiolib.c
diff options
context:
space:
mode:
authorNishanth Menon <nm@ti.com>2014-09-05 14:52:55 -0500
committerLinus Walleij <linus.walleij@linaro.org>2014-09-23 17:51:40 +0200
commit46824e224490af1e6d70fe613930a52253ea969d (patch)
tree2c3fb340abf7e7ab029eea63b9f7ba0f1bc76a6c /drivers/gpio/gpiolib.c
parent9afd23b61221a5c5c0d588f6d8f0e4495ecc8d24 (diff)
downloadlwn-46824e224490af1e6d70fe613930a52253ea969d.tar.gz
lwn-46824e224490af1e6d70fe613930a52253ea969d.zip
gpio: omap: Fix interrupt names
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. Signed-off-by: Nishanth Menon <nm@ti.com> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com> Acked-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk> Acked-by: Kevin Hilman <khilman@linaro.org> Acked-by: Alexandre Courbot <acourbot@nvidia.com> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'drivers/gpio/gpiolib.c')
0 files changed, 0 insertions, 0 deletions