From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>
Cc: linux-acpi@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v3] gpio: acpi: Call enable_irq_wake for _IAE GpioInts with Wake set
Date: Fri, 24 Mar 2017 13:34:03 +0200 [thread overview]
Message-ID: <1490355243.21738.3.camel@linux.intel.com> (raw)
In-Reply-To: <20170324100847.25434-1-hdegoede@redhat.com>
On Fri, 2017-03-24 at 11:08 +0100, Hans de Goede wrote:
> On Bay Trail / Cherry Trail systems with a LID switch, the LID switch
> is
> often connect to a gpioint handled by an _IAE event handler.
> Before this commit such systems would not wake up when opening the
> lid,
> requiring the powerbutton to be pressed after opening the lid to
> wakeup.
>
> Note that Bay Trail / Cherry Trail systems use suspend-to-idle, so
> the interrupts are generated anyway on those lines on lid switch
> changes,
> but they are treated by the IRQ subsystem as spurious while suspended
> if
> not marked as wakeup IRQs.
>
> This commit calls enable_irq_wake() for _IAE GpioInts with a valid
> event handler which have their Wake flag set. This fixes such systems
> not waking up when opening the lid.
>
FWIW:
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> ---
> Changes in v2:
> -Improve commit msg
> -Add Mika's Acked-by
> Changes in v3:
> -Use irqd_is_wakeup_set rather then tracking this ourselves
> ---
> drivers/gpio/gpiolib-acpi.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.c
> index 8cd3f66..2972cad 100644
> --- a/drivers/gpio/gpiolib-acpi.c
> +++ b/drivers/gpio/gpiolib-acpi.c
> @@ -266,6 +266,9 @@ static acpi_status
> acpi_gpiochip_request_interrupt(struct acpi_resource *ares,
> goto fail_free_event;
> }
>
> + if (agpio->wake_capable == ACPI_WAKE_CAPABLE)
> + enable_irq_wake(irq);
> +
> list_add_tail(&event->node, &acpi_gpio->events);
> return AE_OK;
>
> @@ -339,6 +342,9 @@ void acpi_gpiochip_free_interrupts(struct
> gpio_chip *chip)
> list_for_each_entry_safe_reverse(event, ep, &acpi_gpio-
> >events, node) {
> struct gpio_desc *desc;
>
> + if (irqd_is_wakeup_set(irq_get_irq_data(event->irq)))
> + disable_irq_wake(event->irq);
> +
> free_irq(event->irq, event);
> desc = event->desc;
> if (WARN_ON(IS_ERR(desc)))
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-03-24 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 10:08 [PATCH v3] gpio: acpi: Call enable_irq_wake for _IAE GpioInts with Wake set Hans de Goede
2017-03-24 11:34 ` Andy Shevchenko [this message]
2017-03-28 13:23 ` Linus Walleij
2017-03-28 17:24 ` Hans de Goede
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=1490355243.21738.3.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gnurou@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=tiwai@suse.de \
/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).