[roll] Roll fuchsia [perf][ui] Add Scheduled Input event to input_helper

Introduce the ScheduleSimulateButtonPress method to the
fuchsia.ui.test.input FIDL library. This allows clients to schedule a
simulated button press and release event with a specific delay using
the boot timeline.

Update the input-helper component to manage these scheduled events
using the fuchsia.time.alarms.WakeAlarms protocol. This ensures that
events can trigger even if the system is in a low-power state. The
implementation also incorporates wake lease management via the
ActivityGovernor to maintain system wakefulness during event
injection.

Refactor Starnix wakeup tests to utilize this new scheduling
capability. This moves the responsibility of alarm management from the
Starnix kernel module to the specialized input-helper utility,
simplifying the test logic and improving reliability across power
state transitions.

Original-Bug: 483394270

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1500360
Original-Revision: 756b1a1628ae1ec6cbda6107cf4ff7a24ba7516f
GitOrigin-RevId: 951b5954cd7cd58b10bfbdd2e9f530ea60fbe802
Change-Id: I6b6b5a325ce20128a43b5bb9ffc58ccadb2923a4
1 file changed
tree: 46dc03a4bd7c25ff0c4f211b48c9eafe5e1bc873
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.