[roll] Roll fuchsia [amlogic-display] Separate MMIO ranges for GPIO MUX and RESET.

Due to confusion around the CBUS concept (see bug), the amlogic-display
driver has been using the same MMIO register range for EE RESET
registers (on nelson/sherlock/astro boards) and for GPIO Multiplexing
(on the VIM3 board).

To minimize changes for nelson/sherlock/astro, this CL leaves the EE
RESET range where the confusing range used to live, and moves the GPIO
Multiplexing MMIO range.

Original-Bug: 130970
Test: Booted core.vim3 with HDMI monitor to virtcon
Test: Booted core.sherlock to virtcon
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/888092
Original-Revision: 3d47d70c4f1b63eabee70b45d0c988474c241a05
GitOrigin-RevId: 55506ce8a0550ed242e4c5b3d9118d503486d500
Change-Id: I6d78cf3e25903c34f33d98b9461ebe8549bbad6e
1 file changed
tree: 07701a5aafc73132ccde945ec2091dd6d9d6d0f3
  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.