IssueTracker

I believe that would be delays in PR00, not PR01

I also believe (but am not 100% sure) that's coming from the ACPI definitions for the touchscreen: https://source.chromium.org/chromiumos/chromiumos/codesearch/+/main:src/third_party/coreboot/src/mainboard/google/brya/variants/crota/overridetree.cb;l=272;drc=b5891db2438a6e202b3de2b3bd6656bcac103dfe

The delay is unavoidable, although I suppose there's room for improvement on making ACPI power sequencing parallelizable or otherwise deferring it until the device is actually getting probed (preferably using asynchronous probe, since this is a slow device -- ChromeOS tends to configure touchscreen drivers for async probe already, or else loaded as modules).

Perhaps you can take this problem upstream if you'd like to work on something, but from a ChromeOS perspective this is either Intended Behavior or a Feature Request. I don't think we're interested in tracking this as a Feature Request here.