[roll] Roll fuchsia [power] Clarify FIDL protocol usage, update servers

The fuchsia.hardware.powersource/Source protocol was being used
a bit oddly by battery manager. In particular, battery manager
would reconnect to it to get information each time an event was
signaled. This requires far more FIDL interactions.

The protocol was also structured a bit oddly in that changes to
batter information would cause an update event, but the signal
could not be cleared by calling `GetBatteryInfo`. This change
fixes that in the ACPI battery driver and the fake driver.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1148912
Original-Revision: 5450c5ee1771179c9c97f6ae043d93419e66fd21
GitOrigin-RevId: 33d2de837aa06208ff713bdcb95f10aa862ae1cb
Change-Id: I1a57826e51ba640692b28aaa1c6bf69caa925975
1 file changed
tree: d178ba5b110ecf249290da3c257c53c93aebc321
  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.