[PATCH v4 24/80] drm/omap: dsi: move TE GPIO handling into core

[Tomi Valkeinen]

On 08/02/2021 19:55, Tony Lindgren wrote:
> Hi,
> 
> * Tomi Valkeinen <tomi.valkeinen at ti.com> [201124 12:47]:
>> From: Sebastian Reichel <sebastian.reichel at collabora.com>
>>
>> In preparation for removing custom DSS calls from the DSI
>> panel driver, this moves support for external tearing event
>> GPIOs into the DSI host driver. This way tearing events are
>> always handled in the core resulting in simplification of
>> the panel drivers.
>>
>> The TE GPIO acquisition follows works in the same way as the
>> exynos DSI implementation.
> 
> Looks like this patch causes the following warnings:
> 
> DSI: omapdss DSI error: Failed to receive BTA
> DSI: omapdss DSI error: bta sync failed
> DSI: omapdss DSI error: vc(0) busy when trying to config for VP
> DSI: omapdss DSI error: Failed to receive BTA
> DSI: omapdss DSI error: bta sync failed
> DSI: omapdss DSI error: vc(0) busy when trying to config for VP
> DSI: omapdss DSI error: Failed to receive BTA
> DSI: omapdss DSI error: bta sync failed
> DSI: omapdss DSI error: vc(0) busy when trying to config for VP
> ...
> 
> Any ideas? The display works for me despite the constant
> warnings.

Which board is that? Do the errors start right from the boot, or only
after running something in userspace?

 Tomi