linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] video: ARM CLCD: Add DT support
Date: Thu, 12 Sep 2013 22:38:37 +0000	[thread overview]
Message-ID: <20130912223837.GS12758@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <52323E01.2070902@wwwdotorg.org>

On Thu, Sep 12, 2013 at 04:19:45PM -0600, Stephen Warren wrote:
> On 09/12/2013 12:10 PM, Pawel Moll wrote:
> > Such approach would also solve problem with bizarre cases like the
> > Versatile's (not Express ;-) muxer Russell mentioned (where there is a
> > de-facto custom wiring used). And no, I had a look at pinmux bindings
> > and I don't think they fit here at all...
> > 
> > Thoughts?
> 
> I think pinctrl would work just fine here. However, I suspect there's
> little need for pinctrl. pinctrl is required when one module may impose
> requirements on another module's muxable pins. I assume that the
> configuration for pins on CLCD is only relevant for CLCD itself, so
> there's no need to export an interface by which something else can
> configure the pins.

Well, the hardware is much like this:

CLCD ---> Mux ---> output

and the mux is controlled by a register, and will manipulate the output
from the CLCD controller such that the framebuffer contents can be
RGB565, BGR565, XRGB1555, XBGR1555 or RGB888.

(Actually, the Versatile mux can only support one of the 1555 formats,
but I forget which it is.)

I'm not sure that its worth describing all these in DT explicitly, but
maybe encoding it as a special "versatile" version of the CLCD primecell
instead - especially as the external mux takes care of the colour
component order rather than the CLCD controller (and that requires a
bit of board specific code to deal with.)

      reply	other threads:[~2013-09-12 22:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06 17:23 [PATCH 1/2] video: ARM CLCD: Add DT support Pawel Moll
2013-09-06 17:23 ` [PATCH 2/2] ARM: vexpress: Add CLCD Device Tree properties Pawel Moll
2013-09-07 22:55 ` [PATCH 1/2] video: ARM CLCD: Add DT support Sylwester Nawrocki
2013-09-09 11:19   ` Pawel Moll
2013-09-10 21:41     ` Sylwester Nawrocki
2013-09-11 13:43       ` Pawel Moll
2013-09-11 21:14         ` Sylwester Nawrocki
2013-09-12 15:23           ` Pawel Moll
2013-09-12 18:10             ` Pawel Moll
2013-09-12 22:19               ` Stephen Warren
2013-09-12 22:38                 ` Russell King - ARM Linux [this message]

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=20130912223837.GS12758@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).