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 12:02:10 +0200 [thread overview]
Message-ID: <20100811100210.GP17833@buzzloop.caiaq.de> (raw)
In-Reply-To: <AANLkTim+kNyEL2s0k9wLoctRMKDWoaYy66y=adhog1wc@mail.gmail.com>
You dropped all recipients again and only replied to me.
PLEASE DON'T DO THAT.
Always keep all people in the loop, always.
On Wed, Aug 11, 2010 at 01:50:43PM +0400, Yuri Ludkevich wrote:
> 2010/8/11 Daniel Mack <daniel@caiaq.de>
> > According to my reverse engineering, this should be GPIO4_2.
> >
>
> Thanks a lot.
>
> BTW: does /sys/class/gpio/export support GPIOX_2 pins?
Yes, they are aliases to the signals without the "_2" suffix. Quoting
the PXA reference manual, chapter 5.3:
GPIO<6_0>_2:
General-Purpose IO Ports, second instantiation. The same signals as
GPIO<6:0>, but they are given separate names because they are configured
on separate multi-function pins. The recommended configuration is for
both multi-function pin instantiations of these GPIOs not to be
configured simultaneously for GPIO functionality. The preferred
configuration for dual instantiation GPIO usage (that is, using both
GPIO<6:0> and GPIO<6:0>_2 functions) is to configure one multi-function
pin as a GPIO and the second multi-function pin instantiation for an
alternate function other than a GPIO function. Configuring GPIO<6:0> to
be present on two separate multi-function pins is not recommended.
However, when GPIO<6:0> is configured as an output and both
multi-function pin instantiations are programmed for GPIO function, the
primary and secondary instantiation of the multi-function pins are both
outputs from the common GGPIO<6:0> signal. However, when GPIO<6:0> is an
input, the inputs from both multi-function pin instantiations are ORed
together before the result is sent to the internal GPIO<6:0> input
logic.
HTH,
Daniel
next prev parent reply other threads:[~2010-08-11 10:02 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 [this message]
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
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=20100811100210.GP17833@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 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).