diff options
| author | Javier Martinez Canillas | 2016-06-02 16:20:10 +0200 |
|---|---|---|
| committer | Inki Dae | 2016-06-19 07:37:26 +0200 |
| commit | e0d7461ceb5bb9b50e534262eb23e92deaaae6f1 (patch) | |
| tree | 2e9209d93677a68eb100b7f1f4f420088b22d059 /drivers/gpu/drm/exynos/exynos_drm_fimd.c | |
| parent | drm/exynos: fimd: don't set .has_hw_trigger in s3c6400 driver data (diff) | |
| download | kernel-qcow2-linux-e0d7461ceb5bb9b50e534262eb23e92deaaae6f1.tar.gz kernel-qcow2-linux-e0d7461ceb5bb9b50e534262eb23e92deaaae6f1.tar.xz kernel-qcow2-linux-e0d7461ceb5bb9b50e534262eb23e92deaaae6f1.zip | |
drm/exynos: don't use HW trigger for Exynos5420/5422/5800
Commit a6f75aa161c5 ("drm/exynos: fimd: add HW trigger support") added
hardware trigger support to the FIMD controller driver. But this broke
the display in at least the Exynos5800 Peach Pi Chromebook.
So until the issue is fixed, avoid using HW trigger for the Exynos5420
based boards and use SW trigger as it was before the mentioned commit.
Signed-off-by: Javier Martinez Canillas <javier@osg.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.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimd.c b/drivers/gpu/drm/exynos/exynos_drm_fimd.c index 1c23a8ff5e83..f10030ff00e6 100644 --- a/drivers/gpu/drm/exynos/exynos_drm_fimd.c +++ b/drivers/gpu/drm/exynos/exynos_drm_fimd.c @@ -170,14 +170,11 @@ static struct fimd_driver_data exynos5420_fimd_driver_data = { .lcdblk_vt_shift = 24, .lcdblk_bypass_shift = 15, .lcdblk_mic_bypass_shift = 11, - .trg_type = I80_HW_TRG, .has_shadowcon = 1, .has_vidoutcon = 1, .has_vtsel = 1, .has_mic_bypass = 1, .has_dp_clk = 1, - .has_hw_trigger = 1, - .has_trigger_per_te = 1, }; struct fimd_context { |