From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Vittorio Gambaletta (VittGam)" <linuxbugs@vittgam.net>
Cc: linux-kernel@vger.kernel.org, bleung@chromium.org,
bleung@google.com, olof@lixom.net,
Salvatore Bellizzi <lkml@seppia.net>,
groeck@chromium.org, groeck@google.com
Subject: Re: [PATCH RESEND] platform/chrome: cros_ec_lpc: Add support for newer Google devices using custom coreboot firmware or stock SeaBIOS.
Date: Mon, 21 May 2018 14:21:18 -0700 [thread overview]
Message-ID: <20180521212118.GD74396@dtor-ws> (raw)
In-Reply-To: <201805210544.w4L5iZ9B083096@mail.vittgam.net>
Hi Vittorio,
On Mon, May 21, 2018 at 07:44:35AM +0200, Vittorio Gambaletta (VittGam) wrote:
> Custom coreboot firmware does not contain "Google_*" as BIOS
> version string; also, booting through stock SeaBIOS will present
> an empty BIOS version string to Linux. So the generic match at
> the top would not work.
>
> A previous patch added the "GOOGLE" match for DMI system vendor,
> but newer machines such as Skylake-based Caroline use "Google"
> instead.
>
> Also amend the previous comment adding a note that this is needed
> for stock SeaBIOS too.
I think this driver is incorrectly structured and adding new DMI
signatures should not be needed. The newer hardware has the device
GOOG0004 in their ACPI tables, we should not need additional DMI checks.
DMI checks should only be needed for much older hardware, such as
Link/Peppy that did not have EC described in DSDT.
Let me see if I can fix it up.
>
> Signed-off-by: Vittorio Gambaletta <linuxbugs@vittgam.net>
> Signed-off-by: Salvatore Bellizzi <lkml@seppia.net>
>
> ---
>
> --- a/drivers/platform/chrome/cros_ec_lpc.c
> +++ b/drivers/platform/chrome/cros_ec_lpc.c
> @@ -347,7 +347,8 @@
> },
> {
> /*
> - * If the box is running custom coreboot firmware then the
> + * If the box is running custom coreboot firmware,
> + * or is booting Linux through stock SeaBIOS, then the
> * DMI BIOS version string will not be matched by "Google_",
> * but the system vendor string will still be matched by
> * "GOOGLE".
> @@ -358,6 +359,16 @@
> },
> },
> {
> + /*
> + * Newer machines use "Google" instead of "GOOGLE" as
> + * DMI system vendor string.
> + */
> + .matches = {
> + DMI_MATCH(DMI_BIOS_VENDOR, "coreboot"),
> + DMI_MATCH(DMI_SYS_VENDOR, "Google"),
> + },
> + },
> + {
> /* x86-link, the Chromebook Pixel. */
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "GOOGLE"),
Thanks.
--
Dmitry
prev parent reply other threads:[~2018-05-21 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 5:44 [PATCH RESEND] platform/chrome: cros_ec_lpc: Add support for newer Google devices using custom coreboot firmware or stock SeaBIOS Vittorio Gambaletta (VittGam)
2018-05-21 21:21 ` Dmitry Torokhov [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=20180521212118.GD74396@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=bleung@chromium.org \
--cc=bleung@google.com \
--cc=groeck@chromium.org \
--cc=groeck@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxbugs@vittgam.net \
--cc=lkml@seppia.net \
--cc=olof@lixom.net \
/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