From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
To: "Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Andy Shevchenko" <andy@kernel.org>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 2/2] platform/x86: touchscreen_dmi: Consolidate Goodix upside-down touchscreen data
Date: Mon, 12 Feb 2024 17:01:51 -0800 [thread overview]
Message-ID: <a4e81ce3-2ac7-4898-83d2-2907b183fb63@linux.intel.com> (raw)
In-Reply-To: <20240212120608.30469-2-hdegoede@redhat.com>
On 2/12/24 4:06 AM, Hans de Goede wrote:
> Now that prefix matches for ACPI names are supported, the ts_dmi_data
> structs for "GDIX1001:00" and "GDIX1001:01" can be consolidated into
> a single match matching on "GDIX1001".
>
> For consistency also change gdix1002_00_upside_down_data to match.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
Looks good to me.
Reviewed-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
> drivers/platform/x86/touchscreen_dmi.c | 25 ++++++++++---------------
> 1 file changed, 10 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/platform/x86/touchscreen_dmi.c b/drivers/platform/x86/touchscreen_dmi.c
> index 969477c83e56..975cf24ae359 100644
> --- a/drivers/platform/x86/touchscreen_dmi.c
> +++ b/drivers/platform/x86/touchscreen_dmi.c
> @@ -415,18 +415,13 @@ static const struct property_entry gdix1001_upside_down_props[] = {
> { }
> };
>
> -static const struct ts_dmi_data gdix1001_00_upside_down_data = {
> - .acpi_name = "GDIX1001:00",
> +static const struct ts_dmi_data gdix1001_upside_down_data = {
> + .acpi_name = "GDIX1001",
> .properties = gdix1001_upside_down_props,
> };
>
> -static const struct ts_dmi_data gdix1001_01_upside_down_data = {
> - .acpi_name = "GDIX1001:01",
> - .properties = gdix1001_upside_down_props,
> -};
> -
> -static const struct ts_dmi_data gdix1002_00_upside_down_data = {
> - .acpi_name = "GDIX1002:00",
> +static const struct ts_dmi_data gdix1002_upside_down_data = {
> + .acpi_name = "GDIX1002",
> .properties = gdix1001_upside_down_props,
> };
>
> @@ -1412,7 +1407,7 @@ const struct dmi_system_id touchscreen_dmi_table[] = {
> },
> {
> /* Juno Tablet */
> - .driver_data = (void *)&gdix1002_00_upside_down_data,
> + .driver_data = (void *)&gdix1002_upside_down_data,
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "Default string"),
> /* Both product- and board-name being "Default string" is somewhat rare */
> @@ -1658,7 +1653,7 @@ const struct dmi_system_id touchscreen_dmi_table[] = {
> },
> {
> /* Teclast X89 (Android version / BIOS) */
> - .driver_data = (void *)&gdix1001_00_upside_down_data,
> + .driver_data = (void *)&gdix1001_upside_down_data,
> .matches = {
> DMI_MATCH(DMI_BOARD_VENDOR, "WISKY"),
> DMI_MATCH(DMI_BOARD_NAME, "3G062i"),
> @@ -1666,7 +1661,7 @@ const struct dmi_system_id touchscreen_dmi_table[] = {
> },
> {
> /* Teclast X89 (Windows version / BIOS) */
> - .driver_data = (void *)&gdix1001_01_upside_down_data,
> + .driver_data = (void *)&gdix1001_upside_down_data,
> .matches = {
> /* tPAD is too generic, also match on bios date */
> DMI_MATCH(DMI_BOARD_VENDOR, "TECLAST"),
> @@ -1684,7 +1679,7 @@ const struct dmi_system_id touchscreen_dmi_table[] = {
> },
> {
> /* Teclast X98 Pro */
> - .driver_data = (void *)&gdix1001_00_upside_down_data,
> + .driver_data = (void *)&gdix1001_upside_down_data,
> .matches = {
> /*
> * Only match BIOS date, because the manufacturers
> @@ -1788,7 +1783,7 @@ const struct dmi_system_id touchscreen_dmi_table[] = {
> },
> {
> /* "WinBook TW100" */
> - .driver_data = (void *)&gdix1001_00_upside_down_data,
> + .driver_data = (void *)&gdix1001_upside_down_data,
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "WinBook"),
> DMI_MATCH(DMI_PRODUCT_NAME, "TW100")
> @@ -1796,7 +1791,7 @@ const struct dmi_system_id touchscreen_dmi_table[] = {
> },
> {
> /* WinBook TW700 */
> - .driver_data = (void *)&gdix1001_00_upside_down_data,
> + .driver_data = (void *)&gdix1001_upside_down_data,
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "WinBook"),
> DMI_MATCH(DMI_PRODUCT_NAME, "TW700")
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
next prev parent reply other threads:[~2024-02-13 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 12:06 [PATCH 1/2] platform/x86: touchscreen_dmi: Allow partial (prefix) matches for ACPI names Hans de Goede
2024-02-12 12:06 ` [PATCH 2/2] platform/x86: touchscreen_dmi: Consolidate Goodix upside-down touchscreen data Hans de Goede
2024-02-13 1:01 ` Kuppuswamy Sathyanarayanan [this message]
2024-02-12 12:09 ` [PATCH 1/2] platform/x86: touchscreen_dmi: Allow partial (prefix) matches for ACPI names Hans de Goede
2024-02-12 12:36 ` Andy Shevchenko
2024-02-13 1:01 ` Kuppuswamy Sathyanarayanan
2024-02-19 11:42 ` Hans de Goede
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=a4e81ce3-2ac7-4898-83d2-2907b183fb63@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=andy@kernel.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.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