[astro][display] Add VPP, VPU and OSD functionality

With this change, Astro display driver is completely independent of
u-boot display initialization.

The OSD driver is still very rigid. Next step will include writing
a proper OSD driver with its own protocol that could be used by all
AmLogic platforms that use the OSD channel.

The VPU related code contains lots of magic and hardcoded values from
U-Boot due to lack of documentation.

Test: Tested on Astro EVT and P2. Also tested over netboot. Also tested
using various flavors of U-Boot with display initialization ranging from
0 display support to 100% support to make sure what we do on Astro is
truly independent of U-Boot.

Change-Id: Ia02c422bcb462de2774774b6f3c9c6a1661d92bf

[astro][display] Convert astro display driver to cpp

Test: Test on both EVT and P2 units

Change-Id: Iaf6594eebe3edc42fbb2d8f5c61881e7df32d55b

[astro][board][display] Use the new board info to get revision

Test: booted on two version of EVT

Change-Id: Ic64abb62712de4411de9c00d73d5a5e375ceb1e1

[ddk] Rename ZX_PROTOCOL_CANVAS to ZX_PROTOCOL_AMLOGIC_CANVAS

To make it clear that this is an SOC-specific protocol

TEST: boot on VIM2
Change-Id: I0b6c785f77980524d5921fb2a2feda1a8984f8ce

[display] Remove ddk calls from on_displays_changed

This change replaces get_info with per-display argument structs to
on_displays_changed, and it moves the display mode validation to a
posted task. This allow simpler locking in the impl drivers, and it
enables the addition of output parameters into the argument structs.

This change also causes ownership messages to be sent before display
changed messages. Update various clients to not rely on a particular
order of messages.

Test: Boot to virtcon/hotplug on NUC/vim/eve. Run gfxtest, gfxlatency,
and display-test

Change-Id: Id561ed7587037353c1aeeab96511481d74026bdc

[display][astro][vim] Remove fb_vmo

The client now always creates images to be drawn, so don't allocate one
in the display driver itself

Test: boot on vim2 and astro

Change-Id: I96ab7a4cf9acee4ad83314a63f79ee197981c207

[astro][display] Only support EVT units for now

It seems like board rev pins have different values for non-EVT units
and they are not sequentially increasing for newer boards. This code
does a comparison with the EVT board IDs and assume anything else is
not supported

Test: Tested on EVT INX and BOE. Also tested on P2 FF and dev board.

Change-Id: Ica0f0ba28e428a375d2ff1f5ba752cfbb18cae35

[astro][display] First attempt at a proper S905D2 display driver over
MIPI DSI

TEST: tested on EVT Astro with both types of panel. Performed lcd disable from
u-boot and display still came up. Also tested on P2

Change-Id: I5f41d0fb144fb6d404680f09aece4e2e47d15a0e

[public][ddk][framebuffer] Delete display and framebuffer

Test: Boots to virtcon on NUC
Change-Id: Ie1403efb35b8850dae0a29d33a9e871bf00f596e

[astro][display] Add support for canvas driver
zx-2317

Test: Tested on Astro and display came up successfully.

Change-Id: I9196b9fccf867394147f7844fd4dc8f7eaa3e1be

[astro][display] Add vsync interrupt

Change-Id: Ief02057141740637b2aed214c548755bb9bf0d03

[display] Add layers to ddk display protocol

Change-Id: I0e876353121ca8c58bcca4a5c0ada6ee61d0e259

[astro][display] Update Astro's simple display driver to use the new Display API

Change-Id: I9021b715d3c783035712762933e6c2fd4f925066

[astro][display] Basic display driver for Astro

Change-Id: I4f15704bdc6b5f8010803c21f5b85822dcff1182