All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brandon Casey <drafnel@gmail.com>
To: bleung@chromium.org, tzungbi@kernel.org
Cc: chrome-platform@lists.linux.dev, Brandon Casey <drafnel@gmail.com>
Subject: [PATCH] platform/chrome: cros_kbd_led_backlight: support Google Link
Date: Tue, 12 Nov 2024 20:29:05 -0600	[thread overview]
Message-ID: <20241113023800.6263-2-drafnel@gmail.com> (raw)
In-Reply-To: <20241113023800.6263-1-drafnel@gmail.com>

On the Google Pixel chromebook (aka Google Link), the keyboard led
backlight has the ACPI device id "GGL0002".  Let's add it to the
configuration array.

Signed-off-by: Brandon Casey <drafnel@gmail.com>
---
 drivers/platform/chrome/cros_kbd_led_backlight.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/platform/chrome/cros_kbd_led_backlight.c b/drivers/platform/chrome/cros_kbd_led_backlight.c
index 78097c8a4966..5b7766feb10d 100644
--- a/drivers/platform/chrome/cros_kbd_led_backlight.c
+++ b/drivers/platform/chrome/cros_kbd_led_backlight.c
@@ -268,6 +268,7 @@ static int keyboard_led_probe(struct platform_device *pdev)
 #ifdef CONFIG_ACPI
 static const struct acpi_device_id keyboard_led_acpi_match[] = {
 	{ "GOOG0002", (kernel_ulong_t)&keyboard_led_drvdata_acpi },
+	{ "GGL0002", (kernel_ulong_t)&keyboard_led_drvdata_acpi },
 	{ }
 };
 MODULE_DEVICE_TABLE(acpi, keyboard_led_acpi_match);
-- 
2.43.0


  reply	other threads:[~2024-11-13  2:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13  2:29 detect kbd backlight on Google Link (original Chromebook Pixel) Brandon Casey
2024-11-13  2:29 ` Brandon Casey [this message]
2024-11-13  6:46   ` [PATCH] platform/chrome: cros_kbd_led_backlight: support Google Link Tzung-Bi Shih
2024-11-13  8:44     ` Brandon Casey
2024-11-14  2:07       ` Tzung-Bi Shih
2024-11-14  4:38         ` Brandon Casey
2024-11-14  8:53           ` Tzung-Bi Shih
2024-11-18 18:58             ` Brandon Casey
2024-11-21  0:54               ` Tzung-Bi Shih

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=20241113023800.6263-2-drafnel@gmail.com \
    --to=drafnel@gmail.com \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=tzungbi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.