[roll] Roll fuchsia [power] Centralize thermal metric reporting

Currently the ThermalPolicy node calls into PlatformMetrics to log
metrics for thermal load and throttling state. We need to add the same
metrics calls for the ThermalLoadDriver too. However, this gets a little
complicated because some devices use ThermalPolicy (Astro), while others
use ThermalLoadDriver (Nelson), and still others use both (Sherlock).

This change solves the problem by moving the metrics calls out of
ThermalPolicy and into ThermalStateHandler, which is common for all of
the products.

Original-Bug: 86871
Original-Bug: 98245
Test: fx test power-manager-tests
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/683305
Original-Revision: 2cd2c555e5d2f0371e36bdca70ed4ba92635cb86
GitOrigin-RevId: d021af95f37dc19ea7ead77fb07d1dd702912233
Change-Id: I2681e33c275e7189a0bf00be0e5ec5b98608a64d
1 file changed
tree: bb0560db3321513fd9b03233a8f91fc612c4504b
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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.