From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: colibri PXA320 and UCB1400 - touch screen troubles
Date: Wed, 11 Aug 2010 13:24:16 +0200 [thread overview]
Message-ID: <20100811112416.GJ10432@buzzloop.caiaq.de> (raw)
In-Reply-To: <AANLkTik=sT1wtTJRN--t1Q0+Qna6yX+ycbZ-jO5J=iSR@mail.gmail.com>
On Wed, Aug 11, 2010 at 03:10:08PM +0400, Yuri Ludkevich wrote:
> 2010/8/11 Marek Vasut <marek.vasut@gmail.com>
> > Dne St 11. srpna 2010 12:51:25 Daniel Mack napsal(a):
> > > Good. Can you share a patch?
> >
> > nCS3 is the chipselect for CPLD space actually (and the EXT chipselects).
> > If
> > it's configured as nCS3, you can write to the CPLD, but in case you don't
> > need
> > PCMCIA (and ext. chipselects), you should be ok either way.
> >
> > And as Dan said, don't mix GPIO4 and GPIO4_2 :)
> >
> Yep. I know about CPLD. Our board do not use PCMCIA, only SD/MMC. So for us
> it should work.
>
> But if someone wants to use both PCMCIA and touchscreen - how to configure
> this GPIOs properly?
It won't collide. GPIO4 should be configured to the application function
nCS3, and GPIO4_2 is used as GPIO and interrupt input. The signals
aren't shared on the die, and there are two seperate balls (pins) on the
package.
The only limitation is that you can't use them both as GPIOs, because
GPIO register accesses for GPIO4_2 would also affect GPIO4, and
vice-versa.
And in the setup described above, you would just access GPIO4 and be
fine.
Daniel
next prev parent reply other threads:[~2010-08-11 11:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimZeDeS+44=BfchT0gwK5NDLhzLSX1vua8oFBQp@mail.gmail.com>
2010-08-11 8:42 ` colibri PXA320 and UCB1400 - touch screen troubles Marek Vasut
[not found] ` <AANLkTimL7kt0-Do9VQUQvktHfsvdKjm_NJ-eDbxcAu2m@mail.gmail.com>
2010-08-11 9:07 ` Marek Vasut
2010-08-11 9:45 ` Daniel Mack
[not found] ` <AANLkTim+kNyEL2s0k9wLoctRMKDWoaYy66y=adhog1wc@mail.gmail.com>
2010-08-11 10:02 ` Daniel Mack
2010-08-11 10:08 ` Yuri Ludkevich
2010-08-11 10:12 ` Daniel Mack
2010-08-11 10:46 ` Yuri Ludkevich
2010-08-11 10:51 ` Daniel Mack
2010-08-11 10:55 ` Marek Vasut
2010-08-11 11:10 ` Yuri Ludkevich
2010-08-11 11:24 ` Daniel Mack [this message]
2010-08-11 12:32 ` Yuri Ludkevich
2010-08-11 12:35 ` Daniel Mack
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=20100811112416.GJ10432@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.