<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 03:10:08PM +0400, Yuri Ludkevich wrote:<br>
> 2010/8/11 Marek Vasut <<a href="mailto:marek.vasut@gmail.com">marek.vasut@gmail.com</a>><br>
> > Dne St 11. srpna 2010 12:51:25 Daniel Mack napsal(a):<br>
</div><div class="im">> > > Good. Can you share a patch?<br>
> ><br>
> > nCS3 is the chipselect for CPLD space actually (and the EXT chipselects).<br>
> > If<br>
> > it's configured as nCS3, you can write to the CPLD, but in case you don't<br>
> > need<br>
> > PCMCIA (and ext. chipselects), you should be ok either way.<br>
> ><br>
> > And as Dan said, don't mix GPIO4 and GPIO4_2 :)<br>
> ><br>
> Yep. I know about CPLD. Our board do not use PCMCIA, only SD/MMC. So for us<br>
> it should work.<br>
><br>
> But if someone wants to use both PCMCIA and touchscreen - how to configure<br>
> this GPIOs properly?<br>
<br>
</div>It won't collide. GPIO4 should be configured to the application function<br>
nCS3, and GPIO4_2 is used as GPIO and interrupt input. The signals<br>
aren't shared on the die, and there are two seperate balls (pins) on the<br>
package.<br>
<br>
The only limitation is that you can't use them both as GPIOs, because<br>
GPIO register accesses for GPIO4_2 would also affect GPIO4, and<br>
vice-versa.<br>
<br>
And in the setup described above, you would just access GPIO4 and be<br>
fine.<br>
<font color="#888888"><br>
Daniel<br></font></blockquote><div><br>Which list i should use to send patch? <a href="mailto:linux-arm-kernel@lists.infradead.org">linux-arm-kernel@lists.infradead.org</a> or <a href="mailto:openpxa-users@lists.sourceforge.net">openpxa-users@lists.sourceforge.net</a>? or both?<br>
<br>sorry for dumb question, but it my first expirience of sending patches =)<br></div></div><br>