linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: 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: Mon, 20 Dec 2021 18:41:10 -0800	[thread overview]
Message-ID: <YcE+xrSnS7qw0G1/@google.com> (raw)
In-Reply-To: <20211220163823.2.Id022caf53d01112188308520915798f08a33cd3e@changeid>

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);
> +	}
>  
>  	return 0;
>  }

Thanks.

-- 
Dmitry

  reply	other threads:[~2021-12-21  2:41 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 [this message]
2021-12-21 18:13     ` Raul Rangel
2021-12-23 14:42     ` Hans de Goede
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=YcE+xrSnS7qw0G1/@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=dianders@chromium.org \
    --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;
as well as URLs for NNTP newsgroup(s).