Thread (28 messages) flat view 28 messages, 6 authors, 2016-02-15

Re: [PATCH] video: ARM CLCD: Added support for FBIOPAN_DISPLAY and virtual y resolution

From: Arun Ramamurthy <hidden>
Date: 2015-03-02 19:10:05
Also in: linux-devicetree, lkml


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:
quoted
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
A better description (and implementation) would be to describe the size
of the RAM available for video purposes.  The driver can then use the
requested virtual X resolution to limit (and/or compute) the virtual Y
resolution to allow Y panning/wrapping of the display.
In this scenario, where would I specify the virtual X resolution? I am 
assuming it would be in the panel-timing node as Pawel suggested?
This would match some hardware where the video RAM is indeed a separate
physical set of RAM (such as the IM-PD/1).
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help