From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Pawel Moll <pawel.moll@arm.com>
Cc: Mark Rutland <Mark.Rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
Russell King <linux@arm.linux.org.uk>,
Jonathan Austin <Jonathan.Austin@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@linaro.org>,
Will Deacon <Will.Deacon@arm.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 1/2] video: ARM CLCD: Add DT support
Date: Mon, 10 Mar 2014 14:23:21 +0200 [thread overview]
Message-ID: <531DAEB9.3020502@ti.com> (raw)
In-Reply-To: <1394453382.3853.6.camel@hornet>
[-- Attachment #1.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 #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent 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
[not found] ` <1394036606-17784-1-git-send-email-pawel.moll-5wv7dgnIgG8@public.gmane.org>
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
[not found] ` <53184C2E.3000807-l0cyMroinI0@public.gmane.org>
2014-03-06 15:23 ` Pawel Moll
2014-03-07 11:35 ` Tomi Valkeinen
[not found] ` <5319AF00.5030602-l0cyMroinI0@public.gmane.org>
2014-03-10 12:09 ` Pawel Moll
2014-03-10 12:23 ` Tomi Valkeinen [this message]
[not found] ` <531DAEB9.3020502-l0cyMroinI0@public.gmane.org>
2014-03-13 12:01 ` Russell King - ARM Linux
2014-03-13 13:12 ` Pawel Moll
2014-03-13 9:30 ` Linus Walleij
[not found] ` <CACRpkdYBuxYko5JD5ZCfoQq+PeXtkKP9eprk9HM=ghW2YMoMuA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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=Jonathan.Austin@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=Will.Deacon@arm.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pawel.moll@arm.com \
--cc=plagnioj@jcrosoft.com \
/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).