From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] gpiolib: acpi: Add quirk to ignore EC wakeups on Dell Venue 10 Pro 5055
Date: Fri, 2 Apr 2021 21:14:19 +0300 [thread overview]
Message-ID: <YGde+w35hC7bM7Hr@smile.fi.intel.com> (raw)
In-Reply-To: <YGYKbXDu1QlYCXew@smile.fi.intel.com>
On Thu, Apr 01, 2021 at 09:01:17PM +0300, Andy Shevchenko wrote:
> On Thu, Apr 01, 2021 at 06:27:40PM +0200, Hans de Goede wrote:
> > Like some other Bay and Cherry Trail SoC based devices the Dell Venue
> > 10 Pro 5055 has an embedded-controller which uses ACPI GPIO events to
> > report events instead of using the standard ACPI EC interface for this.
> >
> > The EC interrupt is only used to report battery-level changes and
> > it keeps doing this while the system is suspended, causing the system
> > to not stay suspended.
> >
> > Add an ignore-wake quirk for the GPIO pin used by the EC to fix the
> > spurious wakeups from suspend.
>
> Fine by me,
> Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> I have sent my PR to Bart few days ago and today he applied it.
> So, since I'm not expecting much going on in this cycle, I assume
> it's okay to go directly to Bart's tree.
Bart, nevermind, I'll take it thru my tree. It seems we have two and perhaps
even three patches, so it will be easier to handle together.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-04-02 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 16:27 [PATCH] gpiolib: acpi: Add quirk to ignore EC wakeups on Dell Venue 10 Pro 5055 Hans de Goede
2021-04-01 18:01 ` Andy Shevchenko
2021-04-02 18:14 ` Andy Shevchenko [this message]
2021-04-02 18:16 ` Andy Shevchenko
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=YGde+w35hC7bM7Hr@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.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 \
/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