On Wed, Aug 27, 2014 at 08:40:57AM +0100, Mark Brown wrote: > On Tue, Aug 26, 2014 at 08:40:09PM +0200, Henrik Nordström wrote: > > > It is not clear to me where the hardware resources should be listed in > > DT, being it a simplefb node or part of the actual hardware device node > > properly marked as dynamic boot defaults or something else? It's > > somewhere inbetween hardware and virtual device, and somewhat volatile. > > As far as simplefb is concerned it is a hardware desription of the > > framebuffer, but for a kms driver it's no more than firmware handover of > > boottime settings and ceases to exists once the kms driver have > > reconfigured the hardware. > > Is simplefb something that should be in the device tree distinctly in > the first place - shouldn't it be a subset of the functionality of the > video nodes? It's the same hardware being driven differently. Therorically, yes, but that would mean knowing beforehand what the final binding will look like, even before submitting the driver. Since the bindings are always reviewed, and most of the time changed slightly, that wouldn't work very well with the DT as a stable ABI policy I guess. Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
Attachment:
signature.asc
Description: Digital signature
