[roll] Roll fuchsia [fidl][powerlevel] Introduce fuchsia.hardware.powerlevel

Typically the power level for a particular piece of hardware is
configured by requesting a specific voltage to be supplied to that piece
of hardware. In those cases fuchsia.hardware.vreg is a good choice of
FIDL interface.

Some hardware only provides an interface that permits the setting of an
opaque power level. The specific voltages, currents, clock frequencies
that this power level corresponds to is a property of the
implementation.

This FIDL interface provides a mechanism to set the power level for
hardware that only provides an opaque power level as its interface.

Original-Fixed: b/407095566
Test: Linked against a driver and built
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1238719
Original-Revision: 78e0b6b38bcf92e6daba593232afd686bfa23e48
GitOrigin-RevId: 8b339deb0ea0a8b0bd9f6e771888cbabd8272427
Change-Id: I5704c689fa8376e2ced95022e86846ccdfb9d2d4
1 file changed
tree: c5a957920493db83088c76af22464ddc0dbcaa63
  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.