[roll] Roll fuchsia [acpi] Remove AcpiManager's own async::Loop See fxbug.dev/120902 for motivation. Previously, we have already worked to remove custom unmanaged threads from ACPI. This CL replaces the async::Loop in acpi::FuchsiaManager with the current fdf dispatcher. This simplifies the threading story of acpi::Device -- it's initialized, unbound, and destroyed on a synchronized fdf dispatcher, and all FIDL-related accesses also go through the same dispatcher. The only other instance of custom threads I've identified is in GlobalLockHandle. The unit tests are refactored to manually run the loop. This gets rid of a lot of non-determinism since the test can only make forward progress when calling RunUntilIdle. At this point acpi::FuchsiaManager doesn't have any member variables. Perhaps it can even be removed. I'll leave this up to the driver folks to make any desired follow-up changes. Original-Bug: 120902 Run-All-Tests: True Multiply: fuchsia-pkg://fuchsia.com/acpi-board-lib-tests#meta/acpi-board-lib-tests.cm Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/794834 Original-Revision: e325c3ff109c8fdb35ec473ea2c44648857900a8 GitOrigin-RevId: 36213666aa41a292b993f2ee76554b721be0cc7a Change-Id: Ia092673d74281f63692e56a67a669a5df946f2c3
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.