From: Stephen Warren <swarren@wwwdotorg.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/2] video: ARM CLCD: Add DT support
Date: Mon, 23 Sep 2013 16:30:15 +0000 [thread overview]
Message-ID: <52406C97.3010800@wwwdotorg.org> (raw)
In-Reply-To: <20130923160640.GT12758@n2100.arm.linux.org.uk>
On 09/23/2013 10:06 AM, Russell King - ARM Linux wrote:
> On Mon, Sep 23, 2013 at 10:03:18AM -0600, Stephen Warren wrote:
>> It sounds like you could just put LCDControl & 0x2e in the DT rather
>> than using values such as 0x100..0x107, which don't appear to match the
>> register format you mentioned above.
>
> No. Platforms which route the outputs to something like VGA or HDMI can
> change the framebuffer format. Your suggestions is far too restrictive.
Surely the DT should describe the HW setup only. Usually, a particular
HW setup can support multiple different framebuffer formats. Hence, the
DT wouldn't/shouldn't imply anything about the framebuffer format, but
simply which wires are connected to the LCD.
next prev parent reply other threads:[~2013-09-23 16:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 17:18 [PATCH v3 1/2] video: ARM CLCD: Add DT support Pawel Moll
2013-09-16 17:18 ` [PATCH v3 2/2] ARM: vexpress: Add CLCD Device Tree properties Pawel Moll
2013-09-16 19:52 ` [PATCH v3 1/2] video: ARM CLCD: Add DT support Stephen Warren
2013-09-17 16:36 ` Pawel Moll
2013-09-17 16:51 ` Pawel Moll
2013-09-17 21:34 ` Stephen Warren
2013-09-17 21:38 ` Stephen Warren
2013-09-18 16:39 ` Pawel Moll
2013-09-23 16:03 ` Stephen Warren
2013-09-23 16:06 ` Russell King - ARM Linux
2013-09-23 16:30 ` Stephen Warren [this message]
2013-09-23 16:43 ` Russell King - ARM Linux
2013-09-23 19:52 ` Stephen Warren
2013-09-23 20:29 ` Russell King - ARM Linux
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=52406C97.3010800@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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).