From: Wolfram Sang <wsa@kernel.org>
To: Raul E Rangel <rrangel@chromium.org>
Cc: linux-acpi@vger.kernel.org, linux-input@vger.kernel.org,
rafael@kernel.org, timvp@google.com,
mika.westerberg@linux.intel.com,
andriy.shevchenko@linux.intel.com, dmitry.torokhov@gmail.com,
jingle.wu@emc.com.tw, hdegoede@redhat.com,
mario.limonciello@amd.com, linus.walleij@linaro.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 07/13] i2c: acpi: Use ACPI wake capability bit to set wake_irq
Date: Wed, 21 Sep 2022 22:10:45 +0200 [thread overview]
Message-ID: <YytvxVs7g5vx8AAM@shikoro> (raw)
In-Reply-To: <20220921094736.v5.7.I8af4282adc72eb9f247adcd03676a43893a020a6@changeid>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
On Wed, Sep 21, 2022 at 09:51:59AM -0600, Raul E Rangel wrote:
> Device tree already has a mechanism to pass the wake_irq. It does this
> by looking for the wakeup-source property and setting the
> I2C_CLIENT_WAKE flag. This CL adds the ACPI equivalent. It uses the
> ACPI interrupt wake flag to determine if the interrupt can be used to
> wake the system. Previously the i2c drivers had to make assumptions and
> blindly enable the wake IRQ. This can cause spurious wake events. e.g.,
> If there is a device with an Active Low interrupt and the device gets
> powered off while suspending, the interrupt line will go low since it's
> no longer powered and wakes the system. For this reason we should
> respect the board designers wishes and honor the wake bit defined on the
> interrupt.
>
> Signed-off-by: Raul E Rangel <rrangel@chromium.org>
> Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
Acked-by: Wolfram Sang <wsa@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-09-21 20:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 15:51 [PATCH v5 00/13] acpi: i2c: Use SharedAndWake and ExclusiveAndWake to enable wake irq Raul E Rangel
2022-09-21 15:51 ` [PATCH v5 01/13] HID: i2c-hid: Use PM subsystem to manage " Raul E Rangel
2022-09-21 15:51 ` [PATCH v5 02/13] Input: elan_i2c - " Raul E Rangel
2022-09-21 15:51 ` [PATCH v5 03/13] Input: elants_i2c " Raul E Rangel
2022-09-21 15:51 ` [PATCH v5 04/13] Input: raydium_ts_i2c " Raul E Rangel
2022-09-21 15:51 ` [PATCH v5 05/13] gpiolib: acpi: Add wake_capable variants of acpi_dev_gpio_irq_get Raul E Rangel
2022-09-21 15:51 ` [PATCH v5 06/13] ACPI: resources: Add wake_capable parameter to acpi_dev_irq_flags Raul E Rangel
2022-09-21 15:51 ` [PATCH v5 07/13] i2c: acpi: Use ACPI wake capability bit to set wake_irq Raul E Rangel
2022-09-21 20:10 ` Wolfram Sang [this message]
2022-09-21 15:52 ` [PATCH v5 08/13] ACPI: PM: Take wake IRQ into consideration when entering suspend-to-idle Raul E Rangel
2022-09-24 17:00 ` Rafael J. Wysocki
2022-09-28 21:10 ` Raul Rangel
2022-09-29 10:06 ` Rafael J. Wysocki
2022-09-21 15:52 ` [PATCH v5 09/13] HID: i2c-hid: acpi: Stop setting wakeup_capable Raul E Rangel
2022-09-21 15:52 ` [PATCH v5 10/13] HID: i2c-hid: Don't set wake_capable and wake_irq Raul E Rangel
2022-09-21 15:52 ` [PATCH v5 11/13] Input: elan_i2c - " Raul E Rangel
2022-09-21 15:52 ` [PATCH v5 12/13] Input: elants_i2c " Raul E Rangel
2022-09-21 15:52 ` [PATCH v5 13/13] Input: raydium_ts_i2c " Raul E Rangel
2022-09-21 22:54 ` [PATCH v5 00/13] acpi: i2c: Use SharedAndWake and ExclusiveAndWake to enable wake irq Dmitry Torokhov
2022-09-22 10:15 ` Andy Shevchenko
2022-09-23 15:37 ` Raul 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=YytvxVs7g5vx8AAM@shikoro \
--to=wsa@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=jingle.wu@emc.com.tw \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mika.westerberg@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.