2016ë
06ì 10ì¼ 09:24ì Javier Martinez Canillas ì´(ê°) ì´ ê¸:
> Hello Inki,
>
> On Thu, Jun 9, 2016 at 6:35 PM, Inki Dae wrote:
>
> [snip]
>
>>> I know that removing .trg_type is enough but I also removed those lines
>>> because the fields are not used if .trg_type != I80_HW_TRG. So
Hi Javier,
2016ë
06ì 09ì¼ 09:17ì Javier Martinez Canillas ì´(ê°) ì´ ê¸:
> Hello Inki,
>
> Thanks for your feedback.
>
> On 06/08/2016 07:09 PM, Inki Dae wrote:
>> Hi Javier,
>>
>> 2016ë
06ì 02ì¼ 23:20ì Javier Martinez Canillas ì´(ê°) ì´ ê¸:
>>> Commit a6f75aa161c5 ("drm/exy
Hello Inki,
On Thu, Jun 9, 2016 at 6:35 PM, Inki Dae wrote:
[snip]
>> I know that removing .trg_type is enough but I also removed those lines
>> because the fields are not used if .trg_type != I80_HW_TRG. So there is
>> no point to leave a set for unused fields.
>>
>> We can latter add those on
Hi Javier,
2016ë
06ì 02ì¼ 23:20ì Javier Martinez Canillas ì´(ê°) ì´ ê¸:
> 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
Hello Inki,
Thanks for your feedback.
On 06/08/2016 07:09 PM, Inki Dae wrote:
> Hi Javier,
>
> 2016ë
06ì 02ì¼ 23:20ì Javier Martinez Canillas ì´(ê°) ì´ ê¸:
>> Commit a6f75aa161c5 ("drm/exynos: fimd: add HW trigger support") added
>> hardware trigger support to the FIMD controller driv
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 t
