diff options
author | Matt DeVillier <matt.devillier@amd.corp-partner.google.com> | 2022-09-01 15:09:24 -0500 |
---|---|---|
committer | Martin Roth <martin.roth@amd.corp-partner.google.com> | 2022-09-09 03:38:19 +0000 |
commit | 2cf52d80a6ecca97d44d2142521a984df45398f2 (patch) | |
tree | c7fda57c48f4a327c84c30d3937827a40b95ac70 /src/mainboard/google/parrot | |
parent | 003fe294feac303c9b41bf44e7d9965b22758a7d (diff) |
mb/*/{device,override}tree: Set touchpads to use detect (vs probed) flag
Historically, ChromeOS devices have worked around the problem of OEMs
using several different parts for touchpads/touchscreens by using a
ChromeOS kernel-specific 'probed' flag (rejected by the upstream kernel)
to indicate that the device may or may not be present, and that the
driver should probe to confirm device presence.
Since c636142b, coreboot now supports detection for i2c devices at
runtime when creating the device entries for the ACPI/SSDT tables,
rendering the 'probed' flag obsolete for touchpads. Switch all touchpads
in the tree from using the 'probed' flag to the 'detect' flag.
Touchscreens require more involved power sequencing, which will be done
at some future time, after which they will switch over as well.
TEST: build/boot at least one variant for each baseboard in the tree.
Verify touchpad works under Linux and Windows. Verify only a single
touchpad device is present in the ACPI tables.
Change-Id: I47c6eed37eb34c044e27963532e544d3940a7c15
Signed-off-by: Matt DeVillier <matt.devillier@amd.corp-partner.google.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/67305
Reviewed-by: Sean Rhodes <sean@starlabs.systems>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Tim Wawrzynczak <twawrzynczak@chromium.org>
Diffstat (limited to 'src/mainboard/google/parrot')
0 files changed, 0 insertions, 0 deletions