Re: ARM topic: Is DT on ARM the solution, or is there something better?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Thu, Oct 24, 2013 at 11:00:56AM +0200, Thierry Reding wrote:
> On Thu, Oct 24, 2013 at 09:28:11AM +0200, Sascha Hauer wrote:
> > On Wed, Oct 23, 2013 at 09:14:17PM -0400, Rob Clark wrote:
> > > On Mon, Oct 21, 2013 at 5:27 AM, Sascha Hauer <s.hauer@xxxxxxxxxxxxxx> wrote:
> > > >> If a subsystem doesn't work well with DT, then the choices are either:
> > > >>
> > > >> (a) don't use DT with the subsystem
> > > >
> > > > The underlying problem has nothing to do with DT. Multi component
> > > > hardware does exist and won't vanish when we stop using DT.
> > > >
> > > >> (b) fix the subsystem
> > > >
> > > > I'd love to do that. Step one to this seems to be to increase the
> > > > awareness that there's something wrong with DRM.
> > > 
> > > 
> > > Note that I suspect your idea of "fixing drm" is going to break some
> > > userspace assumptions about the hw (ie. userspace isn't expecting
> > > crtcs/encoders/connectors to suddenly appear/disappear.  And the funny
> > > thing is, on all of this hw, that isn't going to happen anyways.
> > 
> > I was talking about all SoC DRM drivers implementing variants of the
> > same glue between drm and the multidevice nature of the components.
> > 
> > To make that sure: I never had the intention to implement hotplug for
> > drm. Also what the imx-drm driver does is not for hotplug, but only for
> > binding different components together.
> 
> I think we should be able to solve that problem generically. Essentially
> we need some sort of composite device that subdevices can register with.
> The composite device can keep track of what devices are needed (this
> works well by walking the device tree, looking for nodes that match by
> compatible and see if their status property is set to"okay") and once
> all of those have been registered do whatever the specific subsystem
> requires.

It would be great to have a generic approach to this since subsystems
like ASoC and v4l2 have the same problem.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux