From e477b0e8de6cd9cf97f381e9ff14934f8ccc33e1 Mon Sep 17 00:00:00 2001 From: Matt DeVillier Date: Thu, 3 Nov 2022 12:43:01 -0500 Subject: [PATCH] Documentation/drivers: Update section on touchscreen runtime detection Update section now that google/skyrim and google/guybrush implement power sequencing and touchscreen runtime detection. Change-Id: Ida63bebf18575d6856edfc65965ff82a4072df87 Signed-off-by: Matt DeVillier Reviewed-on: https://review.coreboot.org/c/coreboot/+/69175 Tested-by: build bot (Jenkins) Reviewed-by: Eric Lai Reviewed-by: Raul Rangel --- Documentation/drivers/dt_entries.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Documentation/drivers/dt_entries.md b/Documentation/drivers/dt_entries.md index 7726b45867..9df965fa0d 100644 --- a/Documentation/drivers/dt_entries.md +++ b/Documentation/drivers/dt_entries.md @@ -162,9 +162,10 @@ I2C audio devices should also work without issue. Touchscreens can use this feature as well, but special care is needed to implement the proper power sequencing for the device to be detected. Generally, this means driving the enable GPIO high and holding the reset GPIO low in early -GPIO init (bootblock/romstage), then releasing reset in ramstage. While no -boards in the tree currently implement this, it has been used in downstream -forks without issue for some time now. +GPIO init (bootblock/romstage), then releasing reset in ramstage. The first +mainboards in the tree to implement this are google/skyrim and google/guybrush. +This feature has also been used in downstream forks without issue for some time +now on several other boards. ### wake