History log of /fuchsia/zircon/system/dev/display/vim-display/rules.mk
Revision Date Author Comments
# 2b29c0bd 10-Sep-2018 David Stevens <stevensd@google.com>

[vim-display] Use core driver edid handling

Test: Boot to virtcon/hotplug/modesetting/audio tone
Change-Id: I75babab8758bb97c1f5ca979c2c11c02ce9c15b6


# 6cce1383 23-Aug-2018 John Bauman <jbauman@google.com>

[vim-display] Switch OSD to use hwreg library

Test: framebuffer on VIM2

Change-Id: I3c853ccc9282b7f7337d55d16cea5c696f114a19


# 36cf959b 11-Jul-2018 John Grossman <johngro@google.com>

[vim][audio] VIM2/S912 SPDIF/HDMI driver

Add support for SPDIF over HDMI on VIM2.

Note: right now, this HDMI driver is taking full control of all of the
audio hardware, and there is a bunch of HDMI specific code which is
leaking into the SPDIF support. When the day comes that we have
proper support for composite devices and we no longer have to merge
the DAI component of the driver with the codec, we can come back here
and properly split the two apart.

Right now, the code is mostly (but not entirely) separated, so it
should be pretty easy to split. Things having to do with format
support, N/CTS calculations, and make/mfr/unique_id, will all come out
of the SPDIF code and become part of the "HDMI codec" half of things,
while all of the functionality for configuring and running the VIM2
SPDIF block should end up in the S912 DAI driver.

Test: Manual on VIM2 hardware
Change-Id: I33a6f5cf9172ec15b2e87839461493b0413ee47e


# a9ff88e1 22-Aug-2018 John Bauman <jbauman@google.com>

[vim-display][display-test] Support NV12 layers

The single fullscreen layer can now use an NV12 image.

Test: display-test

Change-Id: Ie85f91bb4b1ecd5e476012af14fc9d872cccfc46


# 36ee828e 22-Aug-2018 John Bauman <jbauman@google.com>

[vim-display] Convert to C++

This is the minimum change to get it to build as C++ - mainly adding
casts and getting rid of gotos.

Test: vkcube on VIM2.

Change-Id: I4a0008dac5f50ec35c231ccce9fbb082c31dbeaf


# 6bd61ec7 22-Jun-2018 Brijen Raval <braval@google.com>

[amlogic][canvas] Add canvas driver for AMLOGIC

- Added a canvas protocol
- Modified the VIM2 display driver to use the canvas
protocol instead of local canvas driver
- Removed local vim2 canvas driver

ZX-2154 #done

Test: Boot up on VIM2 board with HDMI monitor attached
Change-Id: I9e2328513fafecd1a440985f84ee41fce0c35ab9


# 135847fe 21-Feb-2018 Payam <payamm@google.com>

[zircon][vim2][display] Calculate HDMI timings on the fly
With this change, 1920x1200 finally works and we have 4K support
Removed most of the hardcoded magic.

Change-Id: Icf93b27198e5192ce9ccb12bb1c4c4db008b3831


# 84ede9f3 13-Feb-2018 Payam <payamm@google.com>

[dev][display][vim] Initial support for VIM2 display driver

This is the intial draft. There are still minimal uBoot dependencies (such as hdcp initializations)
and we support very few display resolutions.

Change-Id: Ia5c0b1ba8ad56ccf062960ae6a08d6dcafb62a49


# fdda19c4 30-Jan-2018 Mike Voydanoff <voydanoff@google.com>

[soc][amlogic] Reorganize Amlogic SOC support

Now we have a single system/dev/soc/amlogic directory with
subdirectories of include/ for different Amlogic SOC variants.

Other than the gauss board file, other modules now depend on this
via MODULE_HEADER_DEPS.
The gauss board file still needs to include this as a static library
fora113-clocks.c, but eventually this will likely move to a separate driver
and this will become a header-only module.

Change-Id: I8c3cb5e39e9ed56d56c120e2de435ac020a0e54e


# 2b851ec2 28-Jan-2018 Mike Voydanoff <voydanoff@google.com>

[dev][vim-display] Stop using the bootloader's framebuffer

The VIM display driver now allocates a new buffer for the framebuffer
Display resolution is still hard coded to 1920 x 1080

Change-Id: I0ef0648c55cc62352daf235b4ace1f218692a8da


# d23941e1 29-Nov-2017 Mike Voydanoff <voydanoff@google.com>

[dev][display][vim] Hacked display driver for the Khadas VIM board

This driver merely maps in the framebuffer that was setup by the bootloader.
Only works with displays that have support 1920x1080 resolution.
This is just a stop-gap until we have a proper display driver.

Change-Id: I51417936ceb31f11cc1a426862afcee378567951