On 11/05/2012 02:55 AM, Tomi Valkeinen wrote:
But even then, choosing the manager is not easy, as whoever chooses the
>>manager needs to observe all the possible displays used at the same
>>time...
>
>Right. I was wondering if omapfb/omapdrm could understand the 'all
>possible displays information' better compared to a panel's probe.
>
>Even omapdrm/omafb can't be perfect because we could insert a panel
>driver module at any time, and omapfb/omapdrm may miss that out.
True, omapdrm/fb may have a better idea. It's still unclear though.
Currently we have quite strict order in the sequence the modules need to
be loaded, which is quite bad and causes issues. We should make things
more dynamic, so that the initialization of the drivers could happen
more freely.
But that creates more problems: when booting up, omapfb starts. But
omapfb can't know if all the panel drivers have already been loaded.
omapfb may see that DVI is the default display, but what should it do if
DVI doesn't have a driver yet? It could wait, but perhaps the driver for
DVI will never even be loaded.
The encoder which is connected to the crtc (manager) is picked by
combination of encoder->possible_crtcs bitmask and
connector->best_encoder(). We could keep things limited so that the
association of crtc to encoder (manager to output, roughly) never
changes, but this isn't really the right thing to do. It is better that
the dssdev not rely on knowing the manager it is attached to at probe
time, but instead grab resources more dynamically.
Also, at the moment we don't really have any notification to userspace
about new encoders/connectors showing up (or conversely, being
removed). Only about existing connectors being plugged/unplugged. The
closest analogy is perhaps the USB display devices, but even there it is
only the entire drm device that is plugged/unplugged. And TBH I don't
really see the point in supporting panel drivers being dynamically
loaded. It isn't like someone is dynamically soldering on a new display
connector to some board that is running. I think omapfb or omapdrm
probe should trigger registering the compiled-in panel drivers, so that
it can be sure that the dssdev's pop up before it goes and creates drm
connector objects. Currently we have to hack around this in omapdrm
with late_initcall() to ensure the panel drivers are probed first, but
that is an ugly hack that I'd like to get rid of.
BR,
-R
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
