Re: Binding together tegradrm & nvhost

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

On 21.08.2012 17:57, Thierry Reding wrote:
> Finally the upload is done. You can find my latest work in the next
> branch of the following repository:
> 
> 	git://gitorious.org/linux-tegra-drm/linux-tegra-drm.git
> 
> It's down to two patches and based on next-20120820. Eventually I was
> going to maybe split it up a bit to separate at least the hunks for
> arch/ (Stephen will probably want this anyway) and maybe also some
> functionality like HDMI support.

Hi,

What's the purpose of the drm_clients list? I notice that the drivers
register into that list, but I can't see how the list is used. I feel
like I'm missing something.

This patch ties all of the drivers to host1x. As not all host1x clients
are going to be controlled via DRM, we need to eventually decouple
these. I'm expecting the host1x hardware to controlled by nvhost driver,
and tegradrm will just call nvhost when it needs host1x.

I know it's a bit difficult to understand in concrete terms what I am
after as long as I haven't been upload any code. The memory management
is one obstacle that needs some code before nvhost is usable in upstream
kernel, and lack of device tree support is another.

If you wish me to do the required changes while I'm integrating nvhost,
just let me know.

Terje