[roll] Roll fuchsia [time][power] Skip attempting to update the clock early based on power management signals

The clock must be started before a non-starting update will be permitted
by the kernel (else, BAD_STATE error results).

But since power management updates do not make sense anyways before the
clock is started, it is safe to skip the update altogether.

Original-Bug: b/295537795
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1262924
Original-Revision: 8a6fe745d36d964fe167fe2dd73f48e50f854e50
GitOrigin-RevId: 80b1cf601fa55647a5351da9896d954263da6201
Change-Id: I12e2fc444c46989ef67797ea9b950809314b93f6
1 file changed
tree: bce99d580be1d0180acb724991b08d50ff2fa711
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
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.