From: Hans de Goede <hdegoede@redhat.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>,
jikos@kernel.org, benjamin.tissoires@redhat.com
Cc: anthony.wong@canonical.com,
You-Sheng Yang <vicamo.yang@canonical.com>,
Pavel Balan <admin@kryma.net>, Aaron Ma <aaron.ma@canonical.com>,
HungNien Chen <hn.chen@weidahitech.com>,
Daniel Playfair Cal <daniel.playfair.cal@gmail.com>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] HID: i2c-hid: Enable wakeup capability from Suspend-to-Idle
Date: Thu, 9 Jul 2020 12:05:29 +0200 [thread overview]
Message-ID: <82be7198-168f-d174-7cf8-10cd420e0bb6@redhat.com> (raw)
In-Reply-To: <20200709075731.5046-1-kai.heng.feng@canonical.com>
Hi,
On 7/9/20 9:57 AM, Kai-Heng Feng wrote:
> Many laptops can be woken up from Suspend-to-Idle by touchpad. This is
> also the default behavior on other OSes.
>
> However, if touchpad and touchscreen contact to each other when lid is
> closed, wakeup events can be triggered inadventertly.
>
> So let's disable the wakeup by default, but enable the wakeup capability
> so users can enable it at their own discretion.
>
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
Thank you, this version looks good to me:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
> ---
> v4:
> - Enable the capability, but disable the wakeup default.
>
> v3:
> - Use device_init_wakeup().
> - Wording change.
>
> v2:
> - Fix compile error when ACPI is not enabled.
>
> drivers/hid/i2c-hid/i2c-hid-core.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/hid/i2c-hid/i2c-hid-core.c b/drivers/hid/i2c-hid/i2c-hid-core.c
> index 294c84e136d7..c18ca6a6cb3d 100644
> --- a/drivers/hid/i2c-hid/i2c-hid-core.c
> +++ b/drivers/hid/i2c-hid/i2c-hid-core.c
> @@ -931,6 +931,14 @@ static void i2c_hid_acpi_fix_up_power(struct device *dev)
> acpi_device_fix_up_power(adev);
> }
>
> +static void i2c_hid_acpi_enable_wakeup(struct device *dev)
> +{
> + if (acpi_gbl_FADT.flags & ACPI_FADT_LOW_POWER_S0) {
> + device_set_wakeup_capable(dev, true);
> + device_set_wakeup_enable(dev, false);
> + }
> +}
> +
> static const struct acpi_device_id i2c_hid_acpi_match[] = {
> {"ACPI0C50", 0 },
> {"PNP0C50", 0 },
> @@ -945,6 +953,8 @@ static inline int i2c_hid_acpi_pdata(struct i2c_client *client,
> }
>
> static inline void i2c_hid_acpi_fix_up_power(struct device *dev) {}
> +
> +static inline void i2c_hid_acpi_enable_wakeup(struct device *dev) {}
> #endif
>
> #ifdef CONFIG_OF
> @@ -1072,6 +1082,8 @@ static int i2c_hid_probe(struct i2c_client *client,
>
> i2c_hid_acpi_fix_up_power(&client->dev);
>
> + i2c_hid_acpi_enable_wakeup(&client->dev);
> +
> device_enable_async_suspend(&client->dev);
>
> /* Make sure there is something at this address */
>
next prev parent reply other threads:[~2020-07-09 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 7:57 Kai-Heng Feng
2020-07-09 10:05 ` Hans de Goede [this message]
2020-07-14 13:15 ` Jiri Kosina
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=82be7198-168f-d174-7cf8-10cd420e0bb6@redhat.com \
--to=hdegoede@redhat.com \
--cc=aaron.ma@canonical.com \
--cc=admin@kryma.net \
--cc=anthony.wong@canonical.com \
--cc=benjamin.tissoires@redhat.com \
--cc=daniel.playfair.cal@gmail.com \
--cc=hn.chen@weidahitech.com \
--cc=jikos@kernel.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vicamo.yang@canonical.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
all inboxes | Powered by JetHome®