From: Hans de Goede <hdegoede@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Raul E Rangel <rrangel@chromium.org>
Cc: linux-kernel@vger.kernel.org, mario.limonciello@amd.com,
linux-input@vger.kernel.org, dianders@chromium.org,
"jingle.wu" <jingle.wu@emc.com.tw>
Subject: Re: [PATCH 2/3] Input: elan_i2c - Use PM subsystem to manage wake irq
Date: Thu, 23 Dec 2021 15:42:24 +0100 [thread overview]
Message-ID: <9b004b3d-deed-1b63-2344-a445a9e53b61@redhat.com> (raw)
In-Reply-To: <YcE+xrSnS7qw0G1/@google.com>
Hi,
On 12/21/21 03:41, Dmitry Torokhov wrote:
> Hi Raul,
>
> On Mon, Dec 20, 2021 at 04:43:45PM -0700, Raul E Rangel wrote:
>> @@ -1368,11 +1367,13 @@ static int elan_probe(struct i2c_client *client,
>> }
>>
>> /*
>> - * Systems using device tree should set up wakeup via DTS,
>> + * Systems using device tree or ACPI should set up wakeup via DTS/ACPI,
>> * the rest will configure device as wakeup source by default.
>> */
>> - if (!dev->of_node)
>> + if (!dev->of_node && !ACPI_COMPANION(dev)) {
>
> I think this will break our Rambis that use ACPI for enumeration but
> actually lack _PRW. As far as I remember their trackpads were capable
> of waking up the system.
>
> I think we should remove this chunk completely and instead add necessary
> code to drivers/platform/chrome/chrome-laptop.c (I suppose we need to
> have additional member in struct acpi_peripheral to indicate whether
> device needs to be configured for wakeup and then act upon it in
> chromeos_laptop_adjust_client().
>
>> device_init_wakeup(dev, true);
>> + dev_pm_set_wake_irq(dev, client->irq);
>> + }
As I already mentioned in my other reply in this thread:
https://lore.kernel.org/linux-input/f594afab-8c1a-8821-a775-e5512e17ce8f@redhat.com/
AFAICT most x86 ACPI laptops do not use GPEs for wakeup by touchpad and
as such they do not have a _PRW method.
So for wakeup by elan_i2c touchpads to keep working this code is not
just necessary for some ChromeOS devices, but it is necessary on
most ACPI devices.
The problem of not making these calls on devices where a GPE is actually
used for touchpad wakeup (which at least for now is the exception not
the rule) should probably be fixed by no running this "chunk"
when the device has an ACPI_COMPANION (as this patch already checks)
*and* that ACPI_COMPANION has a valid _PRW method.
Simply removing this chunk, or taking this patch as is will very
likely lead to regressions on various x86 laptop models.
Regards,
Hans
next prev parent reply other threads:[~2021-12-23 14:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 23:43 [PATCH 0/3] Fix spurious wakes on ACPI platforms Raul E Rangel
2021-12-20 23:43 ` [PATCH 1/3] HID: i2c-hid-acpi: Remove explicit device_set_wakeup_capable Raul E Rangel
2021-12-21 18:49 ` Hans de Goede
2021-12-21 23:40 ` Raul Rangel
2021-12-23 8:41 ` Hans de Goede
2021-12-21 23:51 ` Raul Rangel
2021-12-20 23:43 ` [PATCH 2/3] Input: elan_i2c - Use PM subsystem to manage wake irq Raul E Rangel
2021-12-21 2:41 ` Dmitry Torokhov
2021-12-21 18:13 ` Raul Rangel
2021-12-23 14:42 ` Hans de Goede [this message]
2021-12-23 21:21 ` Dmitry Torokhov
2021-12-24 11:11 ` Hans de Goede
2021-12-25 13:51 ` Kai-Heng Feng
2022-01-31 12:41 ` Hans de Goede
2021-12-20 23:43 ` [PATCH 3/3] platform/chrome: cros_ec: Don't enable wake pin if ACPI managed 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=9b004b3d-deed-1b63-2344-a445a9e53b61@redhat.com \
--to=hdegoede@redhat.com \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jingle.wu@emc.com.tw \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=rrangel@chromium.org \
/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®