Searched hist:a392276d1dec63e5aabe6f527c37de29a729559a (Results 1 – 7 of 7) sorted by relevance
| /linux/drivers/gpu/drm/exynos/ |
| H A D | exynos_drm_crtc.h | diff a392276d1dec63e5aabe6f527c37de29a729559a Tue Mar 14 09:27:56 CET 2017 Andrzej Hajda <a.hajda@samsung.com> drm/exynos: move crtc event handling to drivers callbacks
CRTC event is currently send with next vblank, or instantly in case crtc
is being disabled. This approach usually works, but in corner cases it can
result in premature event generation. Only device driver is able to verify
if the event can be sent. This patch is a first step in that direction - it
moves event handling to the drivers.
Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
Signed-off-by: Inki Dae <inki.dae@samsung.com>
|
| H A D | exynos7_drm_decon.c | diff a392276d1dec63e5aabe6f527c37de29a729559a Tue Mar 14 09:27:56 CET 2017 Andrzej Hajda <a.hajda@samsung.com> drm/exynos: move crtc event handling to drivers callbacks
CRTC event is currently send with next vblank, or instantly in case crtc
is being disabled. This approach usually works, but in corner cases it can
result in premature event generation. Only device driver is able to verify
if the event can be sent. This patch is a first step in that direction - it
moves event handling to the drivers.
Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
Signed-off-by: Inki Dae <inki.dae@samsung.com>
|
| H A D | exynos5433_drm_decon.c | diff a392276d1dec63e5aabe6f527c37de29a729559a Tue Mar 14 09:27:56 CET 2017 Andrzej Hajda <a.hajda@samsung.com> drm/exynos: move crtc event handling to drivers callbacks
CRTC event is currently send with next vblank, or instantly in case crtc
is being disabled. This approach usually works, but in corner cases it can
result in premature event generation. Only device driver is able to verify
if the event can be sent. This patch is a first step in that direction - it
moves event handling to the drivers.
Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
Signed-off-by: Inki Dae <inki.dae@samsung.com>
|
| H A D | exynos_drm_crtc.c | diff a392276d1dec63e5aabe6f527c37de29a729559a Tue Mar 14 09:27:56 CET 2017 Andrzej Hajda <a.hajda@samsung.com> drm/exynos: move crtc event handling to drivers callbacks
CRTC event is currently send with next vblank, or instantly in case crtc
is being disabled. This approach usually works, but in corner cases it can
result in premature event generation. Only device driver is able to verify
if the event can be sent. This patch is a first step in that direction - it
moves event handling to the drivers.
Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
Signed-off-by: Inki Dae <inki.dae@samsung.com>
|
| H A D | exynos_drm_vidi.c | diff a392276d1dec63e5aabe6f527c37de29a729559a Tue Mar 14 09:27:56 CET 2017 Andrzej Hajda <a.hajda@samsung.com> drm/exynos: move crtc event handling to drivers callbacks
CRTC event is currently send with next vblank, or instantly in case crtc
is being disabled. This approach usually works, but in corner cases it can
result in premature event generation. Only device driver is able to verify
if the event can be sent. This patch is a first step in that direction - it
moves event handling to the drivers.
Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
Signed-off-by: Inki Dae <inki.dae@samsung.com>
|
| H A D | exynos_mixer.c | diff a392276d1dec63e5aabe6f527c37de29a729559a Tue Mar 14 09:27:56 CET 2017 Andrzej Hajda <a.hajda@samsung.com> drm/exynos: move crtc event handling to drivers callbacks
CRTC event is currently send with next vblank, or instantly in case crtc
is being disabled. This approach usually works, but in corner cases it can
result in premature event generation. Only device driver is able to verify
if the event can be sent. This patch is a first step in that direction - it
moves event handling to the drivers.
Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
Signed-off-by: Inki Dae <inki.dae@samsung.com>
|
| H A D | exynos_drm_fimd.c | diff a392276d1dec63e5aabe6f527c37de29a729559a Tue Mar 14 09:27:56 CET 2017 Andrzej Hajda <a.hajda@samsung.com> drm/exynos: move crtc event handling to drivers callbacks
CRTC event is currently send with next vblank, or instantly in case crtc
is being disabled. This approach usually works, but in corner cases it can
result in premature event generation. Only device driver is able to verify
if the event can be sent. This patch is a first step in that direction - it
moves event handling to the drivers.
Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
Signed-off-by: Inki Dae <inki.dae@samsung.com>
|