summaryrefslogtreecommitdiff
path: root/src/drivers/lenovo
diff options
context:
space:
mode:
authorHung-Te Lin <hungte@chromium.org>2019-02-20 14:31:23 +0800
committerJulius Werner <jwerner@chromium.org>2019-08-15 00:51:31 +0000
commit2c307a0bedfeecd932531387efcc4f66381f6d56 (patch)
tree436305b17e2121e4bf64da4fa46fae4aee49f3e3 /src/drivers/lenovo
parent32ddc0d9f7186471c2f1ae8dc7279639dcaadb06 (diff)
downloadcoreboot-2c307a0bedfeecd932531387efcc4f66381f6d56.tar.xz
mb/google/kukui: Initialize display
Many devices in Kukui family will be using MIPI panels, which needs hard-coded EDID and initialization commands. And because each device may have its own layout and ID, there should be very few devices sharing same panel configuration. As a result, we want to put panel data (EDID and init commands) into board-specific modules, provided by `get_panel_description` function. The panel numeric ID is identified by ADC 2, and is currently available as higher 4 bits of sku_id(). After ID is retrieved, the get_panel_description should return a reference to the EDID and table of init commands. The default implementation is to simply return NULL, and the data for real devices should be provided by panel_*.c in further commits. BUG=b:80501386,b:117254947 BRANCH=none TEST=boot correctly on Kukui Change-Id: I19213aee1ac0f69f42e73be9e5ab72394f412a01 Signed-off-by: Hung-Te Lin <hungte@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/32511 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Julius Werner <jwerner@chromium.org>
Diffstat (limited to 'src/drivers/lenovo')
0 files changed, 0 insertions, 0 deletions