| commit | 08781b48ba4e4efbbedcd7c4b4d0fff399d175b7 | [log] [tgz] |
|---|---|---|
| author | Yilong Li <liyl@fuchsia.infra.roller.google.com> | Wed Jan 03 08:36:32 2024 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jan 03 00:39:18 2024 -0800 |
| tree | 5042f17a3ff61c4e7705779f5391ff00c7ad26e9 | |
| parent | 34b2e06ed3c4d982caffe37918b8dc580539437f [diff] |
[roll] Roll fuchsia [amlogic-display][hpd] Use async loops to handle hotplug IRQs.
Previously, display hotplug IRQs were handled directly by the
zx_interrupt_wait() syscall, on a dedicated IRQ handler thread.
This made it difficult to pause / resume IRQ handling.
This change replaces the interrupt waits with the async::Irq
handler. It binds the interrupt to an async loop (backed by
Zircon ports); interrupts are delivered as packets and handled
by the async IRQ handler running on the loop.
This change doesn't change the HotPlugDetection interface.
Besides, the driver framework v2 prefers drivers to dispatch
asynchronous work on the driver dispatcher over spawning their own
threads. The DFv2 driver dispatcher supports binding async::Irq
and IrqMethod handlers, so this change also makes it easier to migrate
the driver to DFv2 in the future.
Some special configuration of the async loop is needed to support
IRQ binding on the loop. We define this in the hot-plug-detection.cc
as "kIrqHandlerAsyncLoopConfig".
Test: No-op expected.
Test: amlogic-display-test
Test: "display-tool squares" on VIM3 with AML028-30MB-A1 with the
following configurations:
Configuration 1. display is plugged while VIM3 powers on.
Tests passed repeatedly on VIM3.
Configuration 2. Plug the display, run "display-tool squaures",
then unplug the display. Repeat this for 10 times. All the
tests passed.
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/960154
Original-Revision: 173dde97243a8a35585f466977408fc6a8eefe49
GitOrigin-RevId: 1d7f580704c17f290750e10eec2f0d1765181fb7
Change-Id: I0cc8bba1a052ceb93a4e0beac4e922a9ecca1702
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.