Felix Held has submitted this change. ( https://review.coreboot.org/c/coreboot/+/69175 )
Change subject: Documentation/drivers: Update section on touchscreen runtime detection ......................................................................
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 matt.devillier@amd.corp-partner.google.com Reviewed-on: https://review.coreboot.org/c/coreboot/+/69175 Tested-by: build bot (Jenkins) no-reply@coreboot.org Reviewed-by: Eric Lai eric_lai@quanta.corp-partner.google.com Reviewed-by: Raul Rangel rrangel@chromium.org --- M Documentation/drivers/dt_entries.md 1 file changed, 21 insertions(+), 3 deletions(-)
Approvals: build bot (Jenkins): Verified Raul Rangel: Looks good to me, approved Eric Lai: Looks good to me, approved
diff --git a/Documentation/drivers/dt_entries.md b/Documentation/drivers/dt_entries.md index 7726b45..9df965f 100644 --- a/Documentation/drivers/dt_entries.md +++ b/Documentation/drivers/dt_entries.md @@ -162,9 +162,10 @@ 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