summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/exynos/exynos_drm_fimd.c
diff options
context:
space:
mode:
authorHoegeun Kwon2017-02-03 07:12:16 +0100
committerInki Dae2017-02-07 05:54:01 +0100
commit7ff093d09f8f027c317282e18b566473df53e8a1 (patch)
tree17f148c9ca6b127bc43f661c868ac43cf41ec3fd /drivers/gpu/drm/exynos/exynos_drm_fimd.c
parentdrm/exynos/hdmi: add bridge support (diff)
downloadkernel-qcow2-linux-7ff093d09f8f027c317282e18b566473df53e8a1.tar.gz
kernel-qcow2-linux-7ff093d09f8f027c317282e18b566473df53e8a1.tar.xz
kernel-qcow2-linux-7ff093d09f8f027c317282e18b566473df53e8a1.zip
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>
Diffstat (limited to 'drivers/gpu/drm/exynos/exynos_drm_fimd.c')
-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 745cfbdf6b39..a9fa444c6053 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 = {