Thread (1 message) 1 message, 1 author, 2012-07-06

Re: Tegra DRM device tree bindings

From: Stephen Warren <hidden>
Date: 2012-07-06 19:59:13
Also in: dri-devel, linux-tegra

Possibly related (same subject, not in this thread)

On 07/05/2012 06:15 AM, Thierry Reding wrote:
Here's a new proposal that should address all issues collected
during the discussion of the previous one:

From tegra20.dtsi:
...

At a quick glance, that all seems pretty reasonable now.
One problem I've come across when trying to get some rudimentary
code working with this is that there's no longer a device which the
DRM driver can bind to, because the top-level device (host1x) now
has a separate driver.
Can't you just have the host1x driver trigger the instantiation of the
DRM driver? In other words, the host1x node is both the plain host1x
driver and the DRM driver. So, after initializing anything for host1x
itself, just end host1x's probe() with something a call to
drm_platform_init(), passing in host1x's own pdev.

After all, it seems like the whole point of representing host1x in the
DT is to expose the graphics HW, so you'd need the DRM device in that
case.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help