diff options
| author | Dan Murphy <dmurphy@ti.com> | 2012-07-16 13:21:34 -0500 |
|---|---|---|
| committer | Daniel Levin <dendy@ti.com> | 2012-11-28 21:16:23 +0200 |
| commit | 54340708f6e8fffb2353232d461ef8994016daa6 (patch) | |
| tree | 9df831889739cdaa11568345c759e52f477765d2 | |
| parent | c461a99e44264b68b59a361fae38fc3b8c1b2a70 (diff) | |
| download | hardware_ti_omap4-54340708f6e8fffb2353232d461ef8994016daa6.zip hardware_ti_omap4-54340708f6e8fffb2353232d461ef8994016daa6.tar.gz hardware_ti_omap4-54340708f6e8fffb2353232d461ef8994016daa6.tar.bz2 | |
hwc: work-around for panda5 by forcing fake vsync
Panda5 has an HDMI output, but the latest h/w composer api expects
a vsync implementation. A trivial work-around is to go to the previous
api version in which circumstance surfaceflinger will generate 'fake'
vsyncs using a thread and timer.
This can be removed when AVsync is working in the kernel for HDMI
Change-Id: I223db3b69d707cd14f5ab67bedb960ecb3b50f87
Signed-off-by: Dan Murphy <dmurphy@ti.com>
| -rw-r--r-- | hwc/hwc.c | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -2222,6 +2222,11 @@ static int omap4_hwc_device_open(const hw_module_t* module, const char* name, ALOGI("Revert to legacy HWC API for fake vsync"); hwc_dev->base.common.version = HWC_DEVICE_API_VERSION_0_2; } + + if (strncmp("panda5", value, PROPERTY_VALUE_MAX) == 0) { + ALOGI("Revert to legacy HWC API for fake vsync"); + hwc_dev->base.common.version = HWC_DEVICE_API_VERSION_0_2; + } hwc_dev->base.common.module = (hw_module_t *)module; hwc_dev->base.common.close = omap4_hwc_device_close; hwc_dev->base.prepare = omap4_hwc_prepare; |