linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pieterg@gmx.com (pieterg)
To: linux-arm-kernel@lists.infradead.org
Subject: colibri-pxa300: LCD_LDD / LCD_CS gpio conflict
Date: Tue, 7 Sep 2010 09:20:33 +0200	[thread overview]
Message-ID: <201009070920.34414.pieterg@gmx.com> (raw)
In-Reply-To: <AANLkTim+h8Wu40LoWue2=TeKykAJmr8=rT48gF5eCX6j@mail.gmail.com>

On Tuesday 07 September 2010 04:43:31 Eric Miao wrote:
> On Mon, Sep 6, 2010 at 9:12 PM, pieterg <pieterg@gmx.com> wrote:
> > In colibri-pxa300.c, line 132, gpio config GPIO62_LCD_CS_N is
> > overriding the GPIO62_LCD_LDD_8 configuration, earlier in the pin
> > config table.
> >
> > As a result, one pixel data line is missing, obviously causing wrong
> > pixel data on passive lcd panels.
> >
> > Not sure what the best workaround should be.
> > LDD_CS is not available on the colibri evalboard as far as I can see,
> > so we might just define GPIO127_LCD_CS_N instead? (till the soc/carrier
> > board configs have been split)
> >
> > Or for now just put GPIO62_LCD_CS_N between
> > #ifdef ?
>
> Possibly define two groups of LCD pin configurations and select them
> when the appropriate LCD expansion card is plugged. If it can be
> detected at run-time, that will be perfect, otherwise have to come
> up with ugly #ifdef .. #else then.

I don't think you can detect whether an active or passive lcd panel is used.
And since the LCD_CS_N is only used for active panels, we can be sure that 
we only need it when CONFIG_FB_PXA_SMARTPANEL is defined.
So though it's ugly, it is already there, and we can use it.

Rgds, Pieter

  reply	other threads:[~2010-09-07  7:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06 13:12 colibri-pxa300: LCD_LDD / LCD_CS gpio conflict pieterg
2010-09-07  2:43 ` Eric Miao
2010-09-07  7:20   ` pieterg [this message]
2010-09-07  7:29     ` Eric Miao
2010-09-07  9:15       ` pieterg
2010-09-07  9:50         ` Eric Miao
2010-09-07 11:09           ` pieterg

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=201009070920.34414.pieterg@gmx.com \
    --to=pieterg@gmx.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).