[roll] Roll fuchsia [amlogic-display] Use VIU display contents size for capture.

The capture hardware block (VDIN1) of the Amlogic display engine
reads the output of the VIU to the memory. For display capture, the
driver should compare sizes of the destination image (capture buffer)
against the source image (display contents).

This won't cause any behavior difference because the vout size and
the VIU display contents size should always match after applying a
configuration.

Test: flatland_display_compositor_tests
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/966875
Original-Revision: 6979df3283e8f36e9aa455bc0ece05783f1894c4
GitOrigin-RevId: 849c1095315a64623577d7475283443ddfc0e146
Change-Id: I3cb0a6cd13995797ac28bad42d4d12247e0d709c
1 file changed
tree: 53b20d18da2eaa214dbb99226ce2d21ca151260b
  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.