On 09/12/2013 07:03 AM, Pawel Moll wrote: > On Wed, 2013-09-11 at 18:39 +0100, Stephen Warren wrote: ... >> Perhaps the CLCD could reference the memreserve then? > > How do you mean reference the memreserve? It's not a node, I don't think you can get > a phandle to it... Perhaps it's an extension that hasn't actually been implemented yet. I thought I saw some reference to it in some long-past discussions. It's possible that this feature has been dropped in preference to the "CMA" bindings for defining reserved memory regions? ... > Ok, so I'll make it a arm,pl11x,specific property. Actually two > properties - one bit I missed was the dual STN panel case, where they > have separate frame buffers. Something along the lines of: > > Optional: > > - arm,pl11x,framebuffer-base: a pair of two values, address and size, > defining the framebuffer for the upper > (or the only one) panel > - arm,pl11x,lower-framebuffer-base: as above, for the lower STN panel, > when present > > Being very hardware-specific, it covers all possible quirky scenarios, > at the same time does not exclude the option of using the CMA region > phandles, if a particular system needed it. What do "upper" and "lower" mean in this context? I assume this somehow refers to placement of the displays on the board. If so, it sounds like there should be some better terminology; something that's specific to the CLCD controller itself, rather than the environment it's used in. Aalthough it does sound like this is in an FPGA and hence the controller is board-specific, but I don't see why it couldn't be re-used in some other FPGA-based board with different panel layout. Would "A" and "B" or "main" and "primary" or "first" and "second" work better? -- 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
