[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220412212049.gjnel7aubol56azk@earache>
Date: Tue, 12 Apr 2022 16:20:49 -0500
From: Nishanth Menon <nm@...com>
To: Tomi Valkeinen <tomi.valkeinen@...asonboard.com>,
<tony@...mide.com>
CC: Devarsh Thakkar <devarsht@...com>, <linux-kernel@...r.kernel.org>,
<jyri.sarha@....fi>, <tomba@...nel.org>, <airlied@...ux.ie>,
<daniel@...ll.ch>, <dri-devel@...ts.freedesktop.org>,
<a-bhatia1@...com>, <r-ravikumar@...com>, <nikhil.nd@...com>,
<linux-arm-kernel@...ts.infradead.org>, <vigneshr@...com>,
<laurent.pinchart@...asonboard.com>
Subject: Re: [PATCH] drm/tidss: Soft Reset DISPC on startup
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@...asonboard.com>
>
Tony - sysc control for older omap devices still control this directly?
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists