From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: egranata@chromium.org
Cc: hdegoede@redhat.com, dtor@chromium.org,
andy.shevchenko@gmail.com, rafael@kernel.org,
gregkh@linuxfoundation.org, enric.balletbo@collabora.com,
linux-kernel@vger.kernel.org, gwendal@chromium.org,
linux-acpi@vger.kernel.org, briannorris@chromium.org,
andriy.shevchenko@linux.intel.com, egranata@google.com
Subject: Re: [PATCH v2] driver: platform: Support parsing GpioInt 0 in platform_get_irq()
Date: Tue, 12 Feb 2019 11:08:35 +0200 [thread overview]
Message-ID: <20190212090835.GD7875@lahna.fi.intel.com> (raw)
In-Reply-To: <20190211190112.209286-1-egranata@chromium.org>
On Mon, Feb 11, 2019 at 11:01:12AM -0800, egranata@chromium.org wrote:
> From: Enrico Granata <egranata@chromium.org>
>
> 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: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2019-02-12 9:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 18:59 [PATCH] driver: platform: Add support for GpioInt() ACPI to platform_get_irq() egranata
2019-02-07 19:02 ` Rafael J. Wysocki
2019-02-07 19:39 ` Andy Shevchenko
2019-02-07 19:45 ` Andy Shevchenko
2019-02-07 19:55 ` Enrico Granata
[not found] ` <CAPR809vnpuh8nOjU3QMCh6YJUKmtX92+bnHSUKGiAXAp6NwCHQ@mail.gmail.com>
2019-02-07 20:18 ` Andy Shevchenko
2019-02-07 20:29 ` Dmitry Torokhov
2019-02-11 10:30 ` Mika Westerberg
2019-02-11 15:42 ` Hans de Goede
2019-02-11 19:01 ` [PATCH v2] driver: platform: Support parsing GpioInt 0 in platform_get_irq() egranata
2019-02-11 19:25 ` Dmitry Torokhov
2019-02-12 7:29 ` Hans de Goede
2019-02-12 9:08 ` Mika Westerberg [this message]
2019-02-12 9:18 ` Rafael J. Wysocki
2019-02-12 12:46 ` Andy Shevchenko
2019-02-20 18:05 ` Brian Norris
2019-02-21 18:58 ` Enrico Granata
2019-02-21 19:34 ` [PATCH v3] " egranata
2019-02-22 9:03 ` Rafael J. Wysocki
2019-02-22 17:06 ` Brian Norris
2019-02-24 19:34 ` [PATCH v2] " Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190212090835.GD7875@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=briannorris@chromium.org \
--cc=dtor@chromium.org \
--cc=egranata@chromium.org \
--cc=egranata@google.com \
--cc=enric.balletbo@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=gwendal@chromium.org \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).