lkml.org 
[lkml]   [2014]   [Jun]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH v7 1/2] video: ARM CLCD: Add DT support
On 17 June 2014 16:21, Pawel Moll <pawel.moll@arm.com> wrote:
> This patch adds basic DT bindings for the PL11x CLCD cells
> and make their fbdev driver use them.

> +* ARM PrimeCell Color LCD Controller PL110/PL111
> +
> +See also Documentation/devicetree/bindings/arm/primecell.txt
> +
> +Required properties:
> +
> +- compatible: must be one of:
> + "arm,pl110", "arm,primecell"
> + "arm,pl111", "arm,primecell"
> +
> +- reg: base address and size of the control registers block
> +
> +- interrupt-names: either the single entry "combined" representing a
> + combined interrupt output (CLCDINTR), or the four entries
> + "mbe", "vcomp", "lnbu", "fuf" representing the individual
> + CLCDMBEINTR, CLCDVCOMPINTR, CLCDLNBUINTR, CLCDFUFINTR interrupts
> +
> +- interrupts: contains an interrupt specifier for each entry in
> + interrupt-names
> +
> +- clocks-names: should contain "clcdclk" and "apb_pclk"
> +
> +- clocks: contains phandle and clock specifier pairs for the entries
> + in the clock-names property. See
> + Documentation/devicetree/binding/clock/clock-bindings.txt
> +
> +Optional properties:
> +
> +- arm,pl11x,framebuffer-base: a pair of two 32-bit values, address and size,
> + defining the framebuffer that must be used; if not present, the
> + framebuffer may be located anywhere in the memory
> +
> +- max-memory-bandwidth: maximum bandwidth in bytes per second that the
> + cell's memory interface can handle
> +
> +Required sub-nodes:
> +
> +- port: describes LCD panel signals, following the common binding
> + for video transmitter interfaces; see
> + Documentation/devicetree/bindings/media/video-interfaces.txt;
> + when it is a TFT panel, the port's endpoint must define the
> + following property:
> +
> + - arm,pl11x,tft-r0g0b0-pads: an array of three 32-bit values,
> + defining the way CLD pads are wired up; this implicitly
> + defines available color modes, for example:
> + - PL111 TFT 4:4:4 panel:
> + arm,pl11x,tft-r0g0b0-pads = <4 15 20>;
> + - PL110 TFT (1:)5:5:5 panel:
> + arm,pl11x,tft-r0g0b0-pads = <1 7 13>;
> + - PL111 TFT (1:)5:5:5 panel:
> + arm,pl11x,tft-r0g0b0-pads = <3 11 19>;
> + - PL111 TFT 5:6:5 panel:
> + arm,pl11x,tft-r0g0b0-pads = <3 10 19>;
> + - PL110 and PL111 TFT 8:8:8 panel:
> + arm,pl11x,tft-r0g0b0-pads = <0 8 16>;
> + - PL110 and PL111 TFT 8:8:8 panel, R & B components swapped:
> + arm,pl11x,tft-r0g0b0-pads = <16 8 0>;

How does this work for boards like the versatilepb which have a
mux between a PL110 and the TFT, allowing it to efffectively
rewire the pads at runtime under control of the SYS_CLCD
sysreg (to give a wider range of colour modes than the
PL110 supports natively)?

thanks
-- PMM


\
 
 \ /
  Last update: 2014-06-21 01:01    [W:1.944 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site