From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 11/11] ARM: versatile: move CLCD configuration to device tree
Date: Fri, 26 Feb 2016 10:47:04 +0000 [thread overview]
Message-ID: <56D02D28.9080109@ti.com> (raw)
In-Reply-To: <CACRpkdYowXJinONTd2qREfCtEDCon+HSQtdd6t1QQA91f6PJdw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2417 bytes --]
On 25/02/16 21:30, Linus Walleij wrote:
> On Thu, Feb 25, 2016 at 5:45 PM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
>> On 25/02/16 16:04, Linus Walleij wrote:
>
>>> *All* the others
>>> will be very happy with *ONE* display defined as panel in the
>>> device tree, and off they go. Usually VGA. And that will look
>>
>> You keep mentioning VGA. So is there are VGA output? Or do you just mean
>> MIPI DPI panels, which happen to take the same video timings as VGA?
>
> Russell beat me to it, yes there is an external VGA encoder.
> It needs some bits set up through the "misc registers" system
> controller as indicated. From the CLCD hardware point of view
> it's no different than any other panel. So the DTS fragment looks
> like so:
>
> panel {
> compatible = "panel-dpi";
>
> port {
> clcd_panel: endpoint {
> remote-endpoint = <&clcd_pads>;
> };
> };
>
> /* Standard 640x480 VGA timings */
> panel-timing {
> clock-frequency = <25175000>;
> hactive = <640>;
> hback-porch = <48>;
> hfront-porch = <16>;
> hsync-len = <96>;
> vactive = <480>;
> vback-porch = <33>;
> vfront-porch = <10>;
> vsync-len = <2>;
> };
> };
>
>
> This is reported as the default display type if no LCD panel
> is connected.
>
> If a LCD panel is also connected, it take precedence.
Ok. Well... It's all wrong, but I don't know how much time we want to
spend on fixing that.
Although one thing to consider is that if there is ever going to be a
DRM driver for CLCD, it would be good to have the device tree parts
correctly representing the hardware, so that the DRM driver could be
implemented in a cleaner, more generic way.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-26 10:47 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 14:04 [PATCH 00/11] CLCD Nomadik+Versatile support Linus Walleij
2016-02-04 14:04 ` [PATCH 01/11] video: ARM CLCD: backlight support for OF Linus Walleij
2016-02-04 14:04 ` [PATCH 02/11] video: ARM CLCD: support DT signal inversion flags Linus Walleij
2016-02-17 18:10 ` [02/11] " Ray Jui
2016-02-19 8:46 ` Linus Walleij
2016-02-20 1:23 ` Ray Jui
2016-02-20 11:46 ` Linus Walleij
2016-02-04 14:04 ` [PATCH 03/11] video: ARM CLCD: support pads connected in reverse order Linus Walleij
2016-02-04 14:04 ` [PATCH 04/11] video: ARM CLCD: support Nomadik variant Linus Walleij
2016-02-04 14:04 ` [PATCH 05/11] video: ARM CLCD: add special board and panel hooks for Nomadik Linus Walleij
2016-02-04 14:04 ` [PATCH 06/11] Documentation/DT: add blurb for IB2 syscon to Versatile Linus Walleij
2016-02-04 14:04 ` [PATCH 07/11] Documentation/DT: add Versatile display bindings Linus Walleij
2016-02-17 9:11 ` Tomi Valkeinen
2016-02-18 20:48 ` Linus Walleij
2016-02-04 14:04 ` [PATCH 08/11] video: ARM CLCD: add special panel hook for Versatiles Linus Walleij
2016-02-04 14:04 ` [PATCH 09/11] ARM: PB11MPCore: define a standard VGA panel Linus Walleij
2016-02-04 14:04 ` [PATCH 10/11] ARM: PB1176: " Linus Walleij
2016-02-04 14:04 ` [PATCH 11/11] ARM: versatile: move CLCD configuration to device tree Linus Walleij
2016-02-17 9:09 ` Tomi Valkeinen
2016-02-17 9:41 ` Russell King - ARM Linux
2016-02-17 16:17 ` Linus Walleij
2016-02-17 21:32 ` Russell King - ARM Linux
2016-02-18 11:52 ` Tomi Valkeinen
2016-02-18 13:12 ` Russell King - ARM Linux
2016-02-18 13:37 ` Tomi Valkeinen
2016-02-18 20:31 ` Linus Walleij
2016-02-21 22:39 ` Linus Walleij
2016-02-22 15:41 ` Tomi Valkeinen
2016-02-22 15:54 ` Linus Walleij
2016-02-23 9:08 ` Linus Walleij
2016-02-23 9:34 ` Arnd Bergmann
2016-02-23 10:10 ` Linus Walleij
2016-02-23 11:22 ` Arnd Bergmann
2016-02-23 13:00 ` Tomi Valkeinen
2016-02-23 13:16 ` Linus Walleij
2016-02-23 13:38 ` Tomi Valkeinen
2016-02-24 10:53 ` Russell King - ARM Linux
2016-02-24 11:35 ` Tomi Valkeinen
2016-02-25 14:04 ` Linus Walleij
2016-02-25 16:08 ` Arnd Bergmann
2016-02-25 16:22 ` Russell King - ARM Linux
2016-02-25 16:45 ` Tomi Valkeinen
2016-02-25 16:57 ` Russell King - ARM Linux
2016-02-25 19:30 ` Linus Walleij
2016-02-26 10:47 ` Tomi Valkeinen [this message]
2016-03-05 16:57 ` Linus Walleij
2016-03-07 7:36 ` Tomi Valkeinen
2016-02-25 19:32 ` Linus Walleij
2016-02-23 9:58 ` Tomi Valkeinen
2016-02-23 10:32 ` Adam Ford
2016-02-23 10:59 ` Pantelis Antoniou
2016-02-23 11:56 ` Peter Maydell
2016-02-23 12:01 ` Russell King - ARM Linux
2016-02-23 13:45 ` Tom Rini
2016-02-23 12:45 ` Tomi Valkeinen
2016-02-23 13:49 ` Peter Maydell
2016-02-24 12:06 ` Tomi Valkeinen
2016-02-24 10:46 ` Russell King - ARM Linux
2016-02-24 11:21 ` Tomi Valkeinen
2016-02-24 11:35 ` Russell King - ARM Linux
2016-02-24 11:47 ` Tomi Valkeinen
2016-02-24 12:13 ` Pantelis Antoniou
2016-02-25 13:43 ` Linus Walleij
2016-02-25 13:56 ` Tomi Valkeinen
2016-02-25 14:35 ` Pantelis Antoniou
2016-02-25 15:36 ` Linus Walleij
2016-02-25 15:40 ` Pantelis Antoniou
2016-02-23 13:08 ` Linus Walleij
2016-02-15 23:34 ` [PATCH 00/11] CLCD Nomadik+Versatile support Linus Walleij
2016-02-16 13:29 ` Tomi Valkeinen
2016-02-16 22:30 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56D02D28.9080109@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).