From: "Dustin L. Howett" <dustin@howett.net>
To: chrome-platform@lists.linux.dev
Cc: Benson Leung <bleung@chromium.org>,
Aseda Aboagye <aaboagye@chromium.org>,
Tzung-Bi Shih <tzungbi@google.com>,
Michael Niksa <michael.niksa@live.com>,
"Dustin L. Howett" <dustin@howett.net>
Subject: [PATCH v3 1/2] platform/chrome: cros_ec_lpcs: detect the Framework Laptop
Date: Thu, 17 Feb 2022 10:59:29 -0600 [thread overview]
Message-ID: <20220217165930.15081-2-dustin@howett.net> (raw)
In-Reply-To: <20220217165930.15081-1-dustin@howett.net>
The Framework Laptop identifies itself in DMI with manufacturer
"Framework" and product "Laptop".
Signed-off-by: Dustin L. Howett <dustin@howett.net>
---
drivers/platform/chrome/cros_ec_lpc.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/platform/chrome/cros_ec_lpc.c b/drivers/platform/chrome/cros_ec_lpc.c
index d6306d2a096f..458eb59db2ff 100644
--- a/drivers/platform/chrome/cros_ec_lpc.c
+++ b/drivers/platform/chrome/cros_ec_lpc.c
@@ -500,6 +500,14 @@ static const struct dmi_system_id cros_ec_lpc_dmi_table[] __initconst = {
DMI_MATCH(DMI_PRODUCT_NAME, "Glimmer"),
},
},
+ /* A small number of non-Chromebook/box machines also use the ChromeOS EC */
+ {
+ /* the Framework Laptop */
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "Framework"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "Laptop"),
+ },
+ },
{ /* sentinel */ }
};
MODULE_DEVICE_TABLE(dmi, cros_ec_lpc_dmi_table);
--
2.34.1
next prev parent reply other threads:[~2022-02-17 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 16:59 [PATCH v3 0/2] platform/chrome: add support for the Framework Laptop Dustin L. Howett
2022-02-17 16:59 ` Dustin L. Howett [this message]
2022-02-17 16:59 ` [PATCH v3 2/2] platform/chrome: cros_ec_lpcs: reserve the MEC LPC I/O ports first Dustin L. Howett
2022-02-18 2:32 ` [PATCH v3 0/2] platform/chrome: add support for the Framework Laptop Tzung-Bi Shih
2022-05-03 6:10 ` patchwork-bot+chrome-platform
2022-05-04 2:20 ` patchwork-bot+chrome-platform
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=20220217165930.15081-2-dustin@howett.net \
--to=dustin@howett.net \
--cc=aaboagye@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=michael.niksa@live.com \
--cc=tzungbi@google.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