Messages in this thread | | | Date | Mon, 19 May 2014 17:25:40 +0200 | From | Thierry Reding <> | Subject | Re: [PATCH v2 5/7] drm/tegra: Convert to master/component framework |
| |
On Mon, May 19, 2014 at 10:56:08AM +0200, Christian Gmeiner wrote: > 2014-05-13 17:30 GMT+02:00 Thierry Reding <thierry.reding@gmail.com>: > > From: Thierry Reding <treding@nvidia.com> > > > > Instead of the current implementation, reuse the recently introduced > > master/component framework, which is equivalent in most regards. One > > issue is that there is no device to bind the DRM driver to. In order > > to still allow the driver to be probed, expose an interface from the > > host1x device and provide an interface driver to bind to that. > > > > The interface driver then registers (or removes) the master that will be > > used to instantiate and bind the DRM driver. Since the drm_host1x bus > > implementation is now gone the dummy device instantiated by it can no > > longer be used as the parent for the DRM device. However since the > > parent device doesn't need to be modified, the host1x parent device that > > exposes the interface can be used instead. > > > > Signed-off-by: Thierry Reding <treding@nvidia.com> > > Is there a git tree somewhere to have a look at? I am interested in the usage > of the master/component framework.
I've pushed my latest working branches to gitorious[0]. staging/work is the branch that has everything.
Thierry
[0]: https://gitorious.org/thierryreding/linux [unhandled content-type:application/pgp-signature] | |