Re: Binding together tegradrm & nvhost

["Terje Bergström" <tbergstrom-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>]

On 22.08.2012 13:33, Thierry Reding wrote:
> This is used to determine when the DRM driver can be safely initialized.
> Basically the host1x driver scans the DT for display controllers and
> outputs and adds them to this list if they are available. When the
> drivers for those device call host1x_register_client(), they'll be moved
> to the drm_active list and once the the drm_clients list becomes empty,
> the DRM driver is registered using the call to drm_soc_init().

Ok, thanks for clarifying.

> I'm not sure how this can be solved any better than the above. All the
> drivers are inherently tied to host1x anyway. That's why I suggested
> putting the host1x driver along with the DRM driver in the last version
> of these patches so that we can get the initial support written. If the
> functionality is required by other drivers we have two options, either
> the API is exported from the DRM driver or the host1x driver is moved to
> a more central location where other drivers can use it.

Ok, let's go with tight coupling now. Once I have code ready, I'll do
the necessary tricks to do some decoupling.

Terje