Hi,
On Fri, Dec 07, 2012 at 03:12:48PM +0100, Philipp Zabel wrote:
Hi,
Am Montag, den 26.11.2012, 18:56 +0200 schrieb Tomi Valkeinen:
On 2012-11-26 18:10, Steffen Trumtrar wrote:
Hi,
On Mon, Nov 26, 2012 at 04:38:36PM +0200, Tomi Valkeinen wrote:
+optional properties:
+ -
On 2012-12-07 16:12, Philipp Zabel wrote:
Hi,
Am Montag, den 26.11.2012, 18:56 +0200 schrieb Tomi Valkeinen:
So what does the pixelclk-inverted mean? Normally the SoC drives pixel
data on rising edge, and the panel samples it at falling edge? And
vice-versa for inverted? Or the other way
Hi,
Am Montag, den 26.11.2012, 18:56 +0200 schrieb Tomi Valkeinen:
On 2012-11-26 18:10, Steffen Trumtrar wrote:
Hi,
On Mon, Nov 26, 2012 at 04:38:36PM +0200, Tomi Valkeinen wrote:
+optional properties:
+ - hsync-active: hsync pulse is active low/high/ignored
+ - vsync-active:
This adds support for reading display timings from DT into a struct
display_timings. The of_display_timing implementation supports multiple
subnodes. All children are read into an array, that can be queried.
If no native mode is specified, the first subnode will be used.
For cases where the
Hi,
On 2012-11-26 11:07, Steffen Trumtrar wrote:
This adds support for reading display timings from DT into a struct
display_timings. The of_display_timing implementation supports multiple
subnodes. All children are read into an array, that can be queried.
If no native mode is specified,
Hi,
On Mon, Nov 26, 2012 at 04:38:36PM +0200, Tomi Valkeinen wrote:
Hi,
On 2012-11-26 11:07, Steffen Trumtrar wrote:
This adds support for reading display timings from DT into a struct
display_timings. The of_display_timing implementation supports multiple
subnodes. All children are
On 2012-11-26 18:10, Steffen Trumtrar wrote:
Hi,
On Mon, Nov 26, 2012 at 04:38:36PM +0200, Tomi Valkeinen wrote:
+optional properties:
+ - hsync-active: hsync pulse is active low/high/ignored
+ - vsync-active: vsync pulse is active low/high/ignored
+ - de-active: data-enable pulse is
