Re: [PATCH v4 4/5] platform/x86/uniwill: Readd Schenker system vendor for XMG FUSION

[Armin Wolf <W_Armin@gmx.de>]

Am 03.03.26 um 23:54 schrieb Werner Sembach:

> Readd entries with Schenker system vendor for the XMG FUSION, I'm not
> entierly sure if this combi exists, but to be on the safe side to avoid
> regressions.

That was not really what i meant with "preserving the old entries". Please do not
change the system vendor string to "TUXEDO" for the XMG Fusion 15 inside the previous
patch, as this might cause problems when bisecting.

Instead i suggest you do the following:
1. Add two new DMI entries for the XMG Fusion 15 with the "TUXEDO" system vendor string.
2. Apply features across all TUXEDO devices, including the new entries.

This also allows us to backport the patch adding the two new entries.

Thanks,
Armin Wolf

> Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
> ---
>   drivers/platform/x86/uniwill/uniwill-acpi.c | 16 ++++++++++++++++
>   1 file changed, 16 insertions(+)
>
> diff --git a/drivers/platform/x86/uniwill/uniwill-acpi.c b/drivers/platform/x86/uniwill/uniwill-acpi.c
> index 83c60ac6d2fdd..56504e06cfb71 100644
> --- a/drivers/platform/x86/uniwill/uniwill-acpi.c
> +++ b/drivers/platform/x86/uniwill/uniwill-acpi.c
> @@ -2008,6 +2008,22 @@ static struct uniwill_device_descriptor pf5pu1g_descriptor __initdata = {
>   };
>   
>   static const struct dmi_system_id uniwill_dmi_table[] __initconst = {
> +	{
> +		.ident = "XMG FUSION 15 (L19)",
> +		.matches = {
> +			DMI_MATCH(DMI_SYS_VENDOR, "SchenkerTechnologiesGmbH"),
> +			DMI_EXACT_MATCH(DMI_BOARD_NAME, "LAPQC71A"),
> +		},
> +		.driver_data = &lapqc71a_lapqc71b_descriptor,
> +	},
> +	{
> +		.ident = "XMG FUSION 15 (L19)",
> +		.matches = {
> +			DMI_MATCH(DMI_SYS_VENDOR, "SchenkerTechnologiesGmbH"),
> +			DMI_EXACT_MATCH(DMI_BOARD_NAME, "LAPQC71B"),
> +		},
> +		.driver_data = &lapqc71a_lapqc71b_descriptor,
> +	},
>   	{
>   		.ident = "XMG FUSION 15 (L19)",
>   		.matches = {