It could be a pin problem, but I suspect not. The problem seems to be a lack
of a PPS driver. The driver should bind to the pin and provide control
through both /dev and /sys/class/pps, according to linux specs, but I can't
seem to find a driver.
I guess what I'm asking specifically is this; has anybody either gotten PPS
to work with a linux driver on the Overo, or has anybody written their own
driver for it and have some tips?
> I'm not sure if this is exactly the same issue, but I just got through
> enabling some of the GPIO ports on the header of the Palo43 board. The
> problem for me is that they were disabled by the MUX in the u-boot image.
> There's a chance that PPS is disabled there.
> Check out this thread and see if it helps:
> zachlac wrote:
>> I'd like to use the GPIO128_GPS_PPS pps functionality. In defconfig for
>> the Overo I've enabled PPS (CONFIG_PPS=y), but when I install my new
>> kernel I still don't see the PPS devices that the kernel documentation
>> suggests. According to the docs, I should find a /dev entry as well as a
>> /sys/class/pps entry. while /sys/class/pps exists, no devices are
>> Is there a driver I'm missing to enable PPS? Do I need to create my own
>> PPS driver for the kernel, or is one already present?
View this message in context: http://old.nabble.com/PPS-source-tp27341135p27358522.html
Sent from the Gumstix mailing list archive at Nabble.com.