On 17:24-20220412, Tomi Valkeinen wrote:
Hi,
On 14/03/2022 13:37, Devarsh Thakkar wrote:
Soft reset the display subsystem controller on startup and wait for the reset to complete. This helps the scenario where display was already in use by some other core before the linux was booted.
The reason the omapdrm doesn't do a reset is that the PM features on some of the DSS registers were set and controlled outside dss driver, so the dss driver could not do a reset just like that. That design was carried to the tidss driver, although I'm not sure if the reason is valid on AM6 and J7 platforms.
If that reasoning is not valid, this patch is ok and:
Reviewed-by: Tomi Valkeinen tomi.valkeinen@ideasonboard.com
Tony - sysc control for older omap devices still control this directly?