[roll] Roll fuchsia [codec_impl] Allow adapters to set profiles

The CodecImpl library uses a pair of threads internally: a shared_fidl
thread provided by the caller and an internal stream control thread.
Additionally, the DecryptorAdapter has an processing loop thread for
performing decryption operations. As a server library, CodecImpl is
largely unaware of performance or latency requirements, so we should
allow the Codec/DecryptorAdapter implementations set scheduler profiles.

Scheduler profiles can be acquired in a number of ways, but we should
allow CodecImpl users to use the least permissive approach, which is
fuchsia.media.ProfileProvider. That requires the thread handle to be
provided, so this CL exposes the stream control thread and the decryptor
processing thread to the Adapter implementations.

Original-Bug: 67050
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/485520
Original-Revision: 794d562637b7be23760e8077d512bb9cad6161a7
GitOrigin-RevId: 31728a95ea1486f67f42688c092895c9f1bf1f54
Change-Id: I34b9116c97fcdd1cb64db2670cb60904d817b05c
1 file changed
tree: a65e5093eb591bbe8b62e3f47011db897a444dd3
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. flower
  8. jiri.lock
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
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.