From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Hans de Goede <hdegoede@redhat.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Sasha Levin <sashal@kernel.org>,
rafael@kernel.org, linux-acpi@vger.kernel.org
Subject: [PATCH AUTOSEL 4.14 11/11] ACPI: video: Fix Lenovo Ideapad Z570 DMI match
Date: Sun, 26 Feb 2023 09:52:53 -0500 [thread overview]
Message-ID: <20230226145255.829660-11-sashal@kernel.org> (raw)
In-Reply-To: <20230226145255.829660-1-sashal@kernel.org>
From: Hans de Goede <hdegoede@redhat.com>
[ Upstream commit 2d11eae42d52a131f06061015e49dc0f085c5bfc ]
Multiple Ideapad Z570 variants need acpi_backlight=native to force native
use on these pre Windows 8 machines since acpi_video backlight control
does not work here.
The original DMI quirk matches on a product_name of "102434U" but other
variants may have different product_name-s such as e.g. "1024D9U".
Move to checking product_version instead as is more or less standard for
Lenovo DMI quirks for similar reasons.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
drivers/acpi/video_detect.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/video_detect.c b/drivers/acpi/video_detect.c
index 0ec74ab2a3995..b4f16073ef432 100644
--- a/drivers/acpi/video_detect.c
+++ b/drivers/acpi/video_detect.c
@@ -300,7 +300,7 @@ static const struct dmi_system_id video_detect_dmi_table[] = {
.ident = "Lenovo Ideapad Z570",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
- DMI_MATCH(DMI_PRODUCT_NAME, "102434U"),
+ DMI_MATCH(DMI_PRODUCT_VERSION, "Ideapad Z570"),
},
},
{
--
2.39.0
prev parent reply other threads:[~2023-02-26 15:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 14:52 [PATCH AUTOSEL 4.14 01/11] wifi: brcmfmac: Fix potential stack-out-of-bounds in brcmf_c_preinit_dcmds() Sasha Levin
2023-02-26 14:52 ` [PATCH AUTOSEL 4.14 02/11] rcu: Suppress smp_processor_id() complaint in synchronize_rcu_expedited_wait() Sasha Levin
2023-02-26 14:52 ` [PATCH AUTOSEL 4.14 03/11] thermal: intel: Fix unsigned comparison with less than zero Sasha Levin
2023-02-26 14:52 ` [PATCH AUTOSEL 4.14 04/11] timers: Prevent union confusion from unexpected restart_syscall() Sasha Levin
2023-02-26 14:52 ` [PATCH AUTOSEL 4.14 05/11] x86/bugs: Reset speculation control settings on init Sasha Levin
2023-02-26 14:52 ` [PATCH AUTOSEL 4.14 06/11] inet: fix fast path in __inet_hash_connect() Sasha Levin
2023-02-26 14:52 ` [PATCH AUTOSEL 4.14 07/11] ACPI: Don't build ACPICA with '-Os' Sasha Levin
2023-02-26 14:52 ` [PATCH AUTOSEL 4.14 08/11] netpoll: Remove 4s sleep during carrier detection Sasha Levin
2023-02-26 14:52 ` [PATCH AUTOSEL 4.14 09/11] net: bcmgenet: Add a check for oversized packets Sasha Levin
2023-02-26 14:52 ` [PATCH AUTOSEL 4.14 10/11] m68k: Check syscall_trace_enter() return code Sasha Levin
2023-02-26 14:52 ` Sasha Levin [this message]
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=20230226145255.829660-11-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=stable@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