Re: [PATCH v2] drm/exynos/dsi: make te-gpios optional

2017-04-18 Thread Hoegeun Kwon
On 03/15/2017 08:20 PM, Andrzej Hajda wrote: DSI forwards te-gpios interrupts to display controller, but if display controller works in HW-TRIGGER mode this interrupt is not necessary. Making te-gpios property optional allows to avoid generating spare interrupts. With this patch we can get rid of

Re: [PATCH v2] drm/exynos/dsi: make te-gpios optional

2017-03-21 Thread Andrzej Hajda
On 21.03.2017 06:10, Inki Dae wrote: > > 2017년 03월 15일 20:20에 Andrzej Hajda 이(가) 쓴 글: >> DSI forwards te-gpios interrupts to display controller, but if display >> controller works in HW-TRIGGER mode this interrupt is not necessary. >> Making te-gpios property optional allows to avoid generating spa

Re: [PATCH v2] drm/exynos/dsi: make te-gpios optional

2017-03-20 Thread Inki Dae
2017년 03월 15일 20:20에 Andrzej Hajda 이(가) 쓴 글: > DSI forwards te-gpios interrupts to display controller, but if display > controller works in HW-TRIGGER mode this interrupt is not necessary. > Making te-gpios property optional allows to avoid generating spare > interrupts. > With this patch we can

[PATCH v2] drm/exynos/dsi: make te-gpios optional

2017-03-15 Thread Andrzej Hajda
DSI forwards te-gpios interrupts to display controller, but if display controller works in HW-TRIGGER mode this interrupt is not necessary. Making te-gpios property optional allows to avoid generating spare interrupts. With this patch we can get rid of 60 interrupt callbacks per second. Signed-off