On Thu, Oct 18, 2018 at 3:56 PM Robin Murphy <robin.murphy@xxxxxxx> wrote: > On 18/10/18 13:27, Linus Walleij wrote: > > Having failed any attempts at a more generic solution, > > I fall back to the very specific solution: define a simple > > panel for the ARM RTSMv8 emulated platform. > > From the bits of the discussion that I've caught it does seem like this > framebuffer-grovelling business might turn out to be fairly unique to > RTSM/Fast Models, so I guess it's a reasonable compromise. Yeah it's no big deal. > + .compatible = "arm,rtsmv8-display", > > Nit: binding doc? I was actually thinking of not documenting this binding. The DT bindings discussion stalled with supporting virtual stuff and we actually reached the conclusion in a totally different discussion (about gpio-mockup.c) that there is a place for devices which have compatible strings and use the infrastructure but does not have documented bindings. Those devices would be virtual or simulation thingies with no physical real-world counterpart. I don't know for 100% whether I got that right so I'll loop in the DT maintainers for a proper statement. > Nit: "arm,rtsm-display" would probably be a more accurate choice, since > the implementation dates back to long before v8 of anything relevant ;) Works for me :) I'll spin a v2 with that changed. Yours, Linus Walleij
