From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>, Jiri Kosina <jikos@kernel.org>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-input@vger.kernel.org,
"rrangel@chromium.org" <rrangel@chromium.org>,
Hans de Goede <hdegoede@redhat.com>,
Kai-Heng Feng <kai.heng.feng@canonical.com>
Subject: Re: [PATCH] i2c: ACPI: Do not check ACPI_FADT_LOW_POWER_S0
Date: Fri, 5 Aug 2022 11:59:03 -0500 [thread overview]
Message-ID: <1c7fa65d-47ab-b064-9087-648bcfbf4ab5@amd.com> (raw)
In-Reply-To: <12042830.O9o76ZdvQC@kreacher>
On 8/5/2022 11:51, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> The ACPI_FADT_LOW_POWER_S0 flag merely means that it is better to
> use low-power S0 idle on the given platform than S3 (provided that
> the latter is supported) and it doesn't preclude using either of
> them (which of them will be used depends on the choices made by user
> space).
>
> Because of that, ACPI_FADT_LOW_POWER_S0 is generally not sufficient
> for making decisions in device drivers and so i2c_hid_acpi_probe()
> should not use it.
>
> Moreover, Linux always supports suspend-to-idle, so if a given
> device can wake up the system from suspend-to-idle, then it can be
> marked as wakeup capable unconditionally, so make that happen in
> i2c_hid_acpi_probe().
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
+Raul
+Hans
+KH
Raul had a patch that was actually going to just tear out this code
entirely:
https://lkml.kernel.org/lkml/20211220163823.1.Ie20ca47a26d3ea68124d8197b67bb1344c67f650@changeid/
As part of that patch series discussion another suggestion had
transpired
(https://patchwork.kernel.org/project/linux-input/patch/20211220163823.2.Id022caf53d01112188308520915798f08a33cd3e@changeid/#24681016):
```
if ((acpi_gbl_FADT.flags & ACPI_FADT_LOW_POWER_S0) &&
!adev->flags.power_manageable) {
device_set_wakeup_capable(dev, true);
device_set_wakeup_enable(dev, false);
}
```
If this is being changed, maybe consider that suggestion to
check `adev->flags.power_manageable`.
> ---
> drivers/hid/i2c-hid/i2c-hid-acpi.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> Index: linux-pm/drivers/hid/i2c-hid/i2c-hid-acpi.c
> ===================================================================
> --- linux-pm.orig/drivers/hid/i2c-hid/i2c-hid-acpi.c
> +++ linux-pm/drivers/hid/i2c-hid/i2c-hid-acpi.c
> @@ -105,10 +105,8 @@ static int i2c_hid_acpi_probe(struct i2c
>
> acpi_device_fix_up_power(adev);
>
> - if (acpi_gbl_FADT.flags & ACPI_FADT_LOW_POWER_S0) {
> - device_set_wakeup_capable(dev, true);
> - device_set_wakeup_enable(dev, false);
> - }
> + device_set_wakeup_capable(dev, true);
> + device_set_wakeup_enable(dev, false);
>
> return i2c_hid_core_probe(client, &ihid_acpi->ops,
> hid_descriptor_address, 0);
>
>
>
next prev parent reply other threads:[~2022-08-05 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 16:51 [PATCH] i2c: ACPI: Do not check ACPI_FADT_LOW_POWER_S0 Rafael J. Wysocki
2022-08-05 16:59 ` Limonciello, Mario [this message]
2022-08-05 17:08 ` Rafael J. Wysocki
2022-08-05 18:54 ` Hans de Goede
2022-08-06 2:19 ` Raul Rangel
2022-08-08 17:10 ` Rafael J. Wysocki
2022-08-26 21:48 ` Raul Rangel
2022-08-30 17:10 ` Raul 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=1c7fa65d-47ab-b064-9087-648bcfbf4ab5@amd.com \
--to=mario.limonciello@amd.com \
--cc=benjamin.tissoires@redhat.com \
--cc=hdegoede@redhat.com \
--cc=jikos@kernel.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--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