[roll] Roll fuchsia [power-manager] Support CPU thermal client

Currently, there are two different methods for calculating the thermal
load for a given sensor, and both are used to obtain the thermal state
for different clients. The CPU thermal client will use the thermal load
calculated by the ThermalPolicy, and the conversion from thermal load to
thermal state is different from that used by existing thermal clients.
With this change, we will add a new mechanism to route the CPU thermal
load from the ThermalPolicy to the ThermalStateHandler. This will
decouple the CPU thermal load handling from the existing sensor-specific
thermal load handling. Additionally, this change introduces a new toggle
that allows the CPU thermal client to connect to the
`fuchsia.thermal.ClientStateConnector` service and retrieve thermal
state based on CPU thermal load.

Original-Bug: b/295078019, b/320705983
Test: fx test //src/power/power-manager

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/820628
Original-Revision: 3fed7d9afe7f1a796c8eed0fc0de2569f42fa449
GitOrigin-RevId: e62d31bb52ee98ea789646e1bcc798841cac212a
Change-Id: I5d91d1818bc775d8a1bb0556efaebea937fd27ae
1 file changed
tree: bd0fbd9836ed61498fe30818d16fc525862e30d8
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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 via the IRC channel #fuchsia on Freenode.

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.