summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorHoegeun Kwon <hoegeun.kwon@samsung.com>2017-02-03 15:12:16 +0900
committerInki Dae <inki.dae@samsung.com>2017-02-07 13:54:01 +0900
commit7ff093d09f8f027c317282e18b566473df53e8a1 (patch)
tree17f148c9ca6b127bc43f661c868ac43cf41ec3fd
parentaa18157016009b2b63a44e7f29a4f1f46276b5b9 (diff)
downloadop-kernel-dev-7ff093d09f8f027c317282e18b566473df53e8a1.zip
op-kernel-dev-7ff093d09f8f027c317282e18b566473df53e8a1.tar.gz
drm/exynos: fimd: Do not use HW trigger for exynos3250
Commit a6f75aa161c5 ("drm/exynos: fimd: add HW trigger support") added hardware trigger support to the FIMD controller driver. I have tested but this broke the display in at least the exynos3250 Gear 2. So until the issue is fixed, avoid using HW trigger for the exynos3250 based boards and use SW trigger as it was before the mentioned commit. Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com> Signed-off-by: Inki Dae <inki.dae@samsung.com>
-rw-r--r--drivers/gpu/drm/exynos/exynos_drm_fimd.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimd.c b/drivers/gpu/drm/exynos/exynos_drm_fimd.c
index 745cfbd..a9fa444 100644
--- a/drivers/gpu/drm/exynos/exynos_drm_fimd.c
+++ b/drivers/gpu/drm/exynos/exynos_drm_fimd.c
@@ -125,10 +125,8 @@ static struct fimd_driver_data exynos3_fimd_driver_data = {
.timing_base = 0x20000,
.lcdblk_offset = 0x210,
.lcdblk_bypass_shift = 1,
- .trg_type = I80_HW_TRG,
.has_shadowcon = 1,
.has_vidoutcon = 1,
- .has_trigger_per_te = 1,
};
static struct fimd_driver_data exynos4_fimd_driver_data = {
OpenPOWER on IntegriCloud