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 13:09:15 +0200 [thread overview]
Message-ID: <201009071309.15413.pieterg@gmx.com> (raw)
In-Reply-To: <AANLkTinhN-Yz1CMQ78zXSNjjqL-GB1VrBTVKU6A=K9gq@mail.gmail.com>
On Tuesday 07 September 2010 11:50:08 Eric Miao wrote:
> On Tue, Sep 7, 2010 at 5:15 PM, pieterg <pieterg@gmx.com> wrote:
> > How about using GPIO127_LCD_CS_N instead? Then at least we won't have a
> > conflict with the LDD pins.
> > I don't know why the conflicting GPIO62_LCD_CS_N was chosen in the
> > first place?
>
> That depends on hardware, it's not like whichever pin with functionality
> of LCD_CS_N can be used. Need to check with schematics if the LCD_CS_N
> signal is routed to GPIO62 or GPIO127.
GPIO127 is available on the colibri connector (as well as 62 of course), but
on the evalboard, there is no LCD_CS_N support (neither GPIO62 nor
GPIO127).
Rgds, Pieter
prev parent reply other threads:[~2010-09-07 11:09 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
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 [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=201009071309.15413.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).