--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/62afcae0-3fcb-441e-8292-1f39b9b2c8a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
It's been my experience that if you're running 4.x kernel it's best not to use config-pin at all. For simple GPIO it works ok most of the time. But for more complex configurations it may not work all that well. There is at least one GPIO( P9.27 I think ) that won't properly display it's high / low value despite the pin being physically changed. This has been confirmed on our hardware here. This, can be a game changer if you need to monitor the pin states, and you need this pin.