<br><br><div class="gmail_quote">2010/8/11 Daniel Mack <span dir="ltr"><<a href="mailto:daniel@caiaq.de">daniel@caiaq.de</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Wed, Aug 11, 2010 at 02:08:10PM +0400, Yuri Ludkevich wrote:<br>
> 2010/8/11 Daniel Mack <<a href="mailto:daniel@caiaq.de">daniel@caiaq.de</a>><br>
</div><div class="im">> > Yes, they are aliases to the signals without the "_2" suffix. Quoting<br>
> > the PXA reference manual, chapter 5.3:<br>
> ><br>
> > GPIO<6_0>_2:<br>
> ><br>
> > General-Purpose IO Ports, second instantiation. The same signals as<br>
> > GPIO<6:0>, but they are given separate names because they are configured<br>
> > on separate multi-function pins. The recommended configuration is for<br>
> > both multi-function pin instantiations of these GPIOs not to be<br>
> > configured simultaneously for GPIO functionality. The preferred<br>
> > configuration for dual instantiation GPIO usage (that is, using both<br>
> > GPIO<6:0> and GPIO<6:0>_2 functions) is to configure one multi-function<br>
> > pin as a GPIO and the second multi-function pin instantiation for an<br>
> > alternate function other than a GPIO function. Configuring GPIO<6:0> to<br>
> > be present on two separate multi-function pins is not recommended.<br>
> > However, when GPIO<6:0> is configured as an output and both<br>
> > multi-function pin instantiations are programmed for GPIO function, the<br>
> > primary and secondary instantiation of the multi-function pins are both<br>
> > outputs from the common GGPIO<6:0> signal. However, when GPIO<6:0> is an<br>
> > input, the inputs from both multi-function pin instantiations are ORed<br>
> > together before the result is sent to the internal GPIO<6:0> input<br>
> > logic.<br>
><br>
</div><div class="im">> Hmmm. I found with pxaregs tool what both GPIO4 and GPIO4_2 configured as<br>
> GPIO. May be this cause irq autodetection to fail?<br>
<br>
</div>No - if you don't tell the driver which GPIO the interrupt line is<br>
connected to, it can't know. But as the reference manual says, such<br>
configurations should be avoided.<br>
<br>
You're welcome to come up with a patch :)<br>
<font color="#888888"><br>
Daniel<br>
<br></font></blockquote><div>I configure GPIO4 pin as nCS3 (alternate function #1) in colibri-pxa320.c and after that irq autoprobing found valid irq for UCB1400. So touchscreen now working just fine.<br><br>May be I need to check other second instantiation pins for same thing?<br>
<br><br>PS: i am really sorry for may replaying.. i did not notice in time :(<br></div></div><br>