On Fri, Apr 20, 2012 at 02:38:43PM +0200, Thierry Reding wrote:
- Dave Airlie wrote:
I get the feeling the drm can just be a virtual platform device of some sort, then it reads the device tree and binds all the information on what crtc/encoders are available,
That's pretty much what I've come up with in the second round of Tegra DRM patches. Basically display controllers and outputs (RGB, HDMI, TVO, DSI) get separate drivers and register themselves with the DRM driver which then looks at the device tree to see which display controllers to register as CRTCs and parses a list of connector nodes to create encoder/connector pairs that define the physical connectors and their corresponding outputs.
I did take a brief look at the SDRM patches as well and they didn't quite seem to fit what was needed for Tegra. But if time allows I'll take a closer look.
Can you elaborate which parts don't fit? I am very interested to improve this situation, and I think having code to share will be a benefit for us all.
I know that the patches I wrote are no one-solution-fits-for-all yet, they are mainly something to show that drm drivers do not have to be huge complex drivers.
Sascha