Re: [Gumstix-users] Change pinmuxing for GPIOs 127 & 128 in Linux won't work

[Ash C. <as...@gu...>]

Hi,

GPIO127 and GPIO128 aren't actually broken out from the Overo; I
suspect you mean GPIO10 and GPIO186 respectively.

An old version of the Overo footprint confusingly names two signals,
GPIO127_TS_IRQ (J1.8) and GPIO128_GPS_PPS (J1.14).  The signals
document (http://gumstix.org/images/overo_signals_latest.pdf) and all
new versions of the Overo footprint name these two signals much more
appropriately: GPIO10_TS_IRQ and GPIO186_GPS_PPS.

HTH,

Ash

On Thu, Feb 14, 2013 at 11:23 AM, Martin Stoilov <ma...@rp...> wrote:
> I had to change the muxing for GPIO 144, 145 in one of my boards. I did
> omap_mux_init_gpio(144, OMAP_PIN_OUTPUT);
> omap_mux_init_gpio(145, OMAP_PIN_OUTPUT);
> in the board initialization function and it worked fine.
>
> -Martin
>
>
>
> --
> View this message in context: http://gumstix.8.n6.nabble.com/TVP514x-3-5-Kernel-Yocto-tp4966789p4966803.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Free Next-Gen Firewall Hardware Offer
> Buy your Sophos next-gen firewall before the end March 2013
> and get the hardware for free! Learn more.
> http://p.sf.net/sfu/sophos-d2d-feb
> _______________________________________________
> gumstix-users mailing list
> gum...@li...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users