Messages in this thread | | | Date | Tue, 3 Mar 2015 16:31:13 -0800 | From | Arun Ramamurthy <> | Subject | Re: [PATCH] video: ARM CLCD: Added support for FBIOPAN_DISPLAY and virtual y resolution |
| |
On 15-03-02 03:22 PM, Rob Herring wrote: > On Mon, Mar 2, 2015 at 1:09 PM, Arun Ramamurthy > <arun.ramamurthy@broadcom.com> wrote: >> >> >> On 15-03-02 08:11 AM, Russell King - ARM Linux wrote: >>> >>> On Mon, Mar 02, 2015 at 04:08:29PM +0000, Pawel Moll wrote: >>>> >>>> I'm not sure about this... The word "virtual" never works well with >>>> device tree nodes defined as "hardware description". >>>> >>>> I understand what you're doing, but adding this property to the display >>>> controller's node doesn't sound right. How does this describe hardware? >>>> If anywhere, it's more like a job for the panel node? >>> >>> >> I see what you are saying Pawel, I can follow Russell's recommendation of >> adding a RAM size node called max-memory-available or something similar > > We've already got a binding for reserved memory regions for this > purpose. And there is also simplefb binding. > Rob, I am not sure what binding you are referring to, could you be more specific? Also how does the simplefb bindings apply to me considering that is a separate driver? Thanks > Rob >
| |