linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 1/2] video: ARM CLCD: Add DT support
Date: Mon, 10 Mar 2014 12:23:21 +0000	[thread overview]
Message-ID: <531DAEB9.3020502@ti.com> (raw)
In-Reply-To: <1394453382.3853.6.camel@hornet>

[-- Attachment #1: Type: text/plain, Size: 824 bytes --]

On 10/03/14 14:09, Pawel Moll wrote:

>> Note that the same DT bindings you add here should also work for the DRM
>> driver in the future. So, in fact, the question is extended to: will the
>> fbdev 
> 
> No, I don't think so. It's a end of line for it, I believe. From my
> personal point of view the main goal is to fill the last gap between DT
> and non-DT support on one of the Versatile Express boards - CLCD works
> fine when booted with ATAGs, doesn't work when booted with DT. It looks
> bad.

The DT describes the hardware, and there should be only one description
of it, no matter what the used SW is. I see compatible = "arm,pl111" in
the dts. PL111 is the LCD controller, right? What will the DRM driver
use, then, if the "arm,pl111" DT data is designed to work only for the
fbdev?

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2014-03-10 12:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 16:23 [PATCH v5 1/2] video: ARM CLCD: Add DT support Pawel Moll
2014-03-05 16:23 ` [PATCH v5 2/2] ARM: vexpress: Add CLCD Device Tree properties Pawel Moll
2014-03-06 10:21 ` [PATCH v5 1/2] video: ARM CLCD: Add DT support Tomi Valkeinen
2014-03-06 15:23   ` Pawel Moll
2014-03-07 11:35     ` Tomi Valkeinen
2014-03-10 12:09       ` Pawel Moll
2014-03-10 12:23         ` Tomi Valkeinen [this message]
2014-03-13 12:01           ` Russell King - ARM Linux
2014-03-13 13:12           ` Pawel Moll
2014-03-13  9:30   ` Linus Walleij
2014-03-13 11:43     ` Pawel Moll

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=531DAEB9.3020502@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).