From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Raul E Rangel <rrangel@chromium.org>
Cc: linux-acpi@vger.kernel.org, linux-input@vger.kernel.org,
jingle.wu@emc.com.tw, rafael@kernel.org,
andriy.shevchenko@linux.intel.com, mario.limonciello@amd.com,
hdegoede@redhat.com, linus.walleij@linaro.org, timvp@google.com,
dmitry.torokhov@gmail.com, Bartosz Golaszewski <brgl@bgdev.pl>,
Len Brown <lenb@kernel.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 05/13] gpiolib: acpi: Add wake_capable variants of acpi_dev_gpio_irq_get
Date: Thu, 15 Sep 2022 13:43:52 +0300 [thread overview]
Message-ID: <YyMB6Nnp8A8HBeAZ@black.fi.intel.com> (raw)
In-Reply-To: <20220914155914.v3.5.I4ff95ba7e884a486d7814ee888bf864be2ebdef4@changeid>
On Wed, Sep 14, 2022 at 05:57:53PM -0600, Raul E Rangel wrote:
> The ACPI spec defines the SharedAndWake and ExclusiveAndWake share type
> keywords. This is an indication that the GPIO IRQ can also be used as a
> wake source. This change exposes the wake_capable bit so drivers can
> correctly enable wake functionality instead of making an assumption.
>
> Signed-off-by: Raul E Rangel <rrangel@chromium.org>
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2022-09-15 10:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 23:57 [PATCH v3 00/13] acpi: i2c: Use SharedAndWake and ExclusiveAndWake to enable wake irq Raul E Rangel
2022-09-14 23:57 ` [PATCH v3 01/13] HID: i2c-hid: Use PM subsystem to manage " Raul E Rangel
2022-09-14 23:57 ` [PATCH v3 02/13] Input: elan_i2c - " Raul E Rangel
2022-09-14 23:57 ` [PATCH v3 03/13] Input: elants_i2c " Raul E Rangel
2022-09-14 23:57 ` [PATCH v3 04/13] Input: raydium_ts_i2c " Raul E Rangel
2022-09-14 23:57 ` [PATCH v3 05/13] gpiolib: acpi: Add wake_capable variants of acpi_dev_gpio_irq_get Raul E Rangel
2022-09-15 10:43 ` Mika Westerberg [this message]
2022-09-19 9:54 ` Andy Shevchenko
2022-09-19 15:20 ` Raul Rangel
2022-09-14 23:57 ` [PATCH v3 06/13] ACPI: resources: Add wake_capable parameter to acpi_dev_irq_flags Raul E Rangel
2022-09-19 9:54 ` Andy Shevchenko
2022-09-19 15:30 ` Raul Rangel
2022-09-14 23:57 ` [PATCH v3 07/13] i2c: acpi: Use ACPI wake capability bit to set wake_irq Raul E Rangel
2022-09-15 10:46 ` Mika Westerberg
2022-09-15 15:48 ` Raul Rangel
2022-09-19 9:54 ` Andy Shevchenko
2022-09-19 15:38 ` Raul Rangel
2022-09-14 23:57 ` [PATCH v3 08/13] ACPI: PM: Take wake IRQ into consideration when entering suspend-to-idle Raul E Rangel
2022-09-14 23:57 ` [PATCH v3 09/13] HID: i2c-hid: acpi: Stop setting wakeup_capable Raul E Rangel
2022-09-14 23:57 ` [PATCH v3 10/13] HID: i2c-hid: Don't set wake_capable and wake_irq Raul E Rangel
2022-09-14 23:57 ` [PATCH v3 11/13] Input: elan_i2c - " Raul E Rangel
2022-09-14 23:58 ` [PATCH v3 12/13] Input: elants_i2c " Raul E Rangel
2022-09-14 23:58 ` [PATCH v3 13/13] Input: raydium_ts_i2c " Raul E Rangel
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=YyMB6Nnp8A8HBeAZ@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=jingle.wu@emc.com.tw \
--cc=lenb@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=rafael@kernel.org \
--cc=rrangel@chromium.org \
--cc=timvp@google.com \
/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).