Linux-EDAC Archive mirror
 help / color / mirror / Atom feed
From: dengxiang <dengxiang@nfschina.com>
To: lenb@kernel.org, rafael@kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
	platform-driver-x86@vger.kernel.org, wanghuiqiang@huawei.com,
	prime.zeng@hisilicon.com, tony.luck@intel.com
Cc: dengxiang <dengxiang@nfschina.com>
Subject: [PATCH] ACPI: video: Use vendor backlight on Lenovo X1 Carbon.
Date: Mon, 13 May 2024 11:38:34 +0800	[thread overview]
Message-ID: <20240513033834.9174-1-dengxiang@nfschina.com> (raw)

Lenovo X1 Carbon advertises both native and vendor backlight
control interfaces.But Linux defaults to picking the native ACPI
video backlight interface, which will make that the vendor
zx_backlight interface to not work.

Add a DMI quirk to force use of the vendor interface.

Signed-off-by: dengxiang <dengxiang@nfschina.com>
---
 drivers/acpi/video_detect.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/drivers/acpi/video_detect.c b/drivers/acpi/video_detect.c
index 2cc3821b2b16..e647186b4e83 100644
--- a/drivers/acpi/video_detect.c
+++ b/drivers/acpi/video_detect.c
@@ -875,6 +875,14 @@ static const struct dmi_system_id video_detect_dmi_table[] = {
 		DMI_MATCH(DMI_PRODUCT_NAME, "Mipad2"),
 		},
 	},
+	{
+	 .callback = video_detect_force_vendor,
+	 /* Lenovo X1 Carbon */
+	 .matches = {
+		DMI_MATCH(DMI_SYS_VENDOR, "KaiTian"),
+		DMI_MATCH(DMI_PRODUCT_NAME, "KaiTian X1 G1d"),
+		},
+	},
 	{ },
 };
 
-- 
2.30.2


             reply	other threads:[~2024-05-13  3:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13  3:38 dengxiang [this message]
2024-05-13  8:39 ` [PATCH] ACPI: video: Use vendor backlight on Lenovo X1 Carbon Hans de Goede
2024-05-15  3:45   ` dengxiang
2024-05-15 17:29     ` 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=20240513033834.9174-1-dengxiang@nfschina.com \
    --to=dengxiang@nfschina.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=prime.zeng@hisilicon.com \
    --cc=rafael@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=wanghuiqiang@huawei.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).