summaryrefslogtreecommitdiffstats
path: root/.mailmap
diff options
context:
space:
mode:
authorEnrico Granata <egranata@chromium.org>2019-02-11 20:01:12 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-02-12 10:36:49 +0100
commitdaaef255dc96834aaaad627d3271504cba3ac2dc (patch)
tree7aca979c0f93f168e293a0b941e510e575abec6f /.mailmap
parentMerge tag 'topic/component-typed-2019-02-11' of git://anongit.freedesktop.org... (diff)
downloadlinux-daaef255dc96834aaaad627d3271504cba3ac2dc.tar.xz
linux-daaef255dc96834aaaad627d3271504cba3ac2dc.zip
driver: platform: Support parsing GpioInt 0 in platform_get_irq()
ACPI 5 added support for GpioInt resources as a way to provide information about interrupts mediated via a GPIO controller. Several device buses (e.g. SPI, I2C) have support for retrieving an IRQ specified via this type of resource, and providing it directly to the driver as an IRQ number. This is not currently done for the platform drivers, as platform_get_irq() does not try to parse GpioInt() resources. This requires drivers to either have to support only one possible IRQ resource, or to have code in place to try both as a failsafe. While there is a possibility of ambiguity for devices that exposes multiple IRQs, it is easy and feasible to support the common case of devices that only expose one IRQ which would be of either type depending on the underlying system's architecture. This commit adds support for parsing a GpioInt resource in order to fulfill a request for the index 0 IRQ for a platform device. Signed-off-by: Enrico Granata <egranata@chromium.org> Reviewed-by: Dmitry Torokhov <dtor@chromium.org> Acked-by: Hans de Goede <hdegoede@redhat.com> Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com> Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions