From: Philipp Zabel <philipp.zabel@gmail.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: rafael@kernel.org, linux-kernel@vger.kernel.org,
catalin@antebit.com, travisghansen@yahoo.com,
Shyam-sundar.S-k@amd.com, Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 1/6] acpi/x86: s2idle: Move _HID handling for AMD systems into structures
Date: Tue, 13 Sep 2022 18:44:03 +0200 [thread overview]
Message-ID: <YyCzU12b+bX3yvvu@rog> (raw)
In-Reply-To: <20220912172401.22301-2-mario.limonciello@amd.com>
Am Mon, Sep 12, 2022 at 12:23:55PM -0500 schrieb Mario Limonciello:
> Right now the information about which cases to use for what are in a
> comment, but this is error prone. Instead move all information into
> a dedicated structure.
>
> Tested-by: catalin@antebit.com
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> drivers/acpi/x86/s2idle.c | 63 ++++++++++++++++++++++++++++-----------
> 1 file changed, 46 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/acpi/x86/s2idle.c b/drivers/acpi/x86/s2idle.c
> index f9ac12b778e6..a7757551f750 100644
> --- a/drivers/acpi/x86/s2idle.c
> +++ b/drivers/acpi/x86/s2idle.c
> @@ -363,6 +363,39 @@ static int validate_dsm(acpi_handle handle, const char *uuid, int rev, guid_t *d
> return ret;
> }
>
> +struct amd_lps0_hid_device_data {
> + const unsigned int rev_id;
> + const bool check_off_by_one;
> + const bool prefer_amd_guid;
> +};
> +
> +static const struct amd_lps0_hid_device_data amd_picasso = {
> + .rev_id = 0,
> + .check_off_by_one = true,
> + .prefer_amd_guid = false,
> +};
> +
> +static const struct amd_lps0_hid_device_data amd_cezanne = {
> + .rev_id = 0,
> + .check_off_by_one = false,
> + .prefer_amd_guid = false,
> +};
> +
> +static const struct amd_lps0_hid_device_data amd_rembrandt = {
> + .rev_id = 2,
> + .check_off_by_one = false,
> + .prefer_amd_guid = true,
> +};
> +
> +static const struct acpi_device_id amd_hid_ids[] = {
> + {"AMD0004", (kernel_ulong_t)&amd_picasso, },
> + {"AMD0005", (kernel_ulong_t)&amd_picasso, },
> + {"AMDI0005", (kernel_ulong_t)&amd_picasso, },
> + {"AMDI0006", (kernel_ulong_t)&amd_cezanne, },
> + {"AMDI0007", (kernel_ulong_t)&amd_rembrandt, },
> + {}
> +};
> +
> static int lps0_device_attach(struct acpi_device *adev,
> const struct acpi_device_id *not_used)
> {
> @@ -370,31 +403,27 @@ static int lps0_device_attach(struct acpi_device *adev,
> return 0;
>
> if (acpi_s2idle_vendor_amd()) {
> - /* AMD0004, AMD0005, AMDI0005:
> - * - Should use rev_id 0x0
> - * - function mask > 0x3: Should use AMD method, but has off by one bug
> - * - function mask = 0x3: Should use Microsoft method
> - * AMDI0006:
> - * - should use rev_id 0x0
> - * - function mask = 0x3: Should use Microsoft method
> - * AMDI0007:
> - * - Should use rev_id 0x2
> - * - Should only use AMD method
> - */
> - const char *hid = acpi_device_hid(adev);
> - rev_id = strcmp(hid, "AMDI0007") ? 0 : 2;
> + static const struct acpi_device_id *dev_id;
> + const struct amd_lps0_hid_device_data *data;
> +
> + for (dev_id = &amd_hid_ids[0]; dev_id->id[0]; dev_id++)
> + if (acpi_dev_hid_uid_match(adev, dev_id->id, NULL))
> + break;
> + if (dev_id != NULL)
> + data = (const struct amd_lps0_hid_device_data *) dev_id->driver_data;
> + else
> + return 0;
The "!= NULL" seems unnecessary, I would change this to:
+ if (!dev_id)
+ return 0;
+ data = (const struct amd_lps0_hid_device_data *) dev_id->driver_data;
But either way,
Reviewed-by: Philipp Zabel <philipp.zabel@gmail.com>
Tested-by: Philipp Zabel <philipp.zabel@gmail.com> # GA402RJ
regards
Philipp
next prev parent reply other threads:[~2022-09-13 17:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 17:23 [PATCH v2 0/6] Fixups for s2idle on various Rembrandt laptops Mario Limonciello
2022-09-12 17:23 ` [PATCH v2 1/6] acpi/x86: s2idle: Move _HID handling for AMD systems into structures Mario Limonciello
2022-09-13 16:44 ` Philipp Zabel [this message]
2022-09-12 17:23 ` [PATCH v2 2/6] acpi/x86: s2idle: If a new AMD _HID is missing assume Rembrandt Mario Limonciello
2022-09-13 16:46 ` Philipp Zabel
2022-09-12 17:23 ` [PATCH v2 3/6] acpi/x86: s2idle: Add module parameter to prefer Microsoft GUID Mario Limonciello
2022-09-13 16:47 ` Philipp Zabel
2022-09-12 17:23 ` [PATCH v2 4/6] acpi/x86: s2idle: Add a quirk for ASUS TUF Gaming A17 FA707RE Mario Limonciello
2022-09-13 16:48 ` Philipp Zabel
2022-09-12 17:23 ` [PATCH v2 5/6] acpi/x86: s2idle: Add a quirk for ASUS ROG Zephyrus G14 Mario Limonciello
2022-09-13 16:50 ` Philipp Zabel
2022-09-15 3:22 ` Matthew Anderson
2022-09-15 3:48 ` Matthew Anderson
2022-09-12 17:24 ` [PATCH v2 6/6] acpi/x86: s2idle: Add a quirk for Lenovo Slim 7 Pro 14ARH7 Mario Limonciello
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=YyCzU12b+bX3yvvu@rog \
--to=philipp.zabel@gmail.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=catalin@antebit.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=rafael@kernel.org \
--cc=travisghansen@yahoo.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