Beaglebone and GPIO

[Aleksandr Rybalko]

On Mon, 28 Jan 2013 10:28:14 +0100
Damjan Marion <damjan.marion at gmail.com> wrote:

> 
> On Jan 28, 2013, at 6:34 AM, Emmanuel Vadot <elbarto at megadrive.org> wrote:
> 
> > On Mon, 28 Jan 2013 04:45:11 +0100
> > Emmanuel Vadot <elbarto at megadrive.org> wrote:
> > 
> >> 
> >> Hello,
> >> 
> >> I've filled the missings pads on am335x_scm_padconf.c so every GPIO pin is now accessible (if, of course, they are in GPIO mode).
> >> 
> >> I've also corrected/enhanced an error on ti_gpio.c, in the ti_gpio_pin_get function then code was testing if the pin was in output mode and if it was return EINVAL but in fact it was returning EINVAL if the pin was in input mode.
> >> Now the function return the value of the pin despite of it's an input or output. (seems more logical to me but I'm open to discuss this).
> >> 
> >> I've also patched gpioctl(1), it now test if the pin is in GPIO mode (according to the pin mux setting) and print either the value or "Not in GPIO mode".
> >> 
> >> Cheers,
> > 
> > Attached is the coorect patch with the correct case for some signals names.
> 
> Hell, Thanks for diffs.
> 
> padconf stuff is committed. For gpio changes would like to have blessing from gonzo.
> 
> Gonzo, are you fine with gpio changes?
> 
> Damjan
> 
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"

Hi!

No-no-no, guys, please don't do that. I'm working on Freescale i.MX5
support, and it have way to read pin input even if another controller
drives that pin (If I understand doc correct :) ).  

Thanks!

WBW
-- 
Aleksandr Rybalko <ray at ddteam.net>