Hi, On Thu, Mar 23, 2017 at 09:08:18AM +0200, Tomi Valkeinen wrote: > On 23/03/17 08:31, Sebastian Reichel wrote: > > >> It shouldn't matter when omapdrm is initialized. omapdrm should wait > >> until it has all the displays. > > > > I tried to trace this. I assume, that your "should wait until it has > > all the displays" refers to the code in "omap_connect_dssdevs()". > > Unfortunately that code does not work correctly: > > Indeed, sorry about the confusion. Apparently I was talking about TI's > kernel, which has fixes for this. > > I have actually posted the patches, along with a lot of other stuff, > last Nov. See "[PATCH 00/36] drm/omap: miscallaneous improvements" > series. The patches 23-25 should fix this particular issue. Ok, I got both initializing correctly by cherry-picking (and rebasing) the following patches: drm/omap: Use omapdss_stack_is_ready() to check that the display stack is up drm/omap: dss: Support for detecting display stack readiness drm/omap: move dss_initialized to omapdss-base drm/omap: add omapdss-base.ko drm/omap: dss: Functions to check components in the display/output list What's the plan with regarding patchset? -- Sebastian
Attachment:
signature.asc
Description: PGP signature
