Re: imx27: pinctrl: GPIO set output value failed

Chris Ruehl <[email protected]> Mon, 20 Jan 2014 12:32:22 +0800
Newsgroups gmane.linux.ports.arm.general
Message-ID <[email protected]>
>
> Hi Markus,
>
> Its very confusing what the mxc driver is doing, I'd enabled the 
> debugging and the
> kernel spits out this:
>
> root@gtsir20:~# dmesg | tail -2
> [   43.683766] mxc: set GPIO 9 to high trigger
> [   44.766186] mxc: switch GPIO 9 to low trigger
> root@gtsir20:~# echo 0 > /sys/class/gpio/gpio9/value
> root@gtsir20:~# echo 1 > /sys/class/gpio/gpio9/value
> root@gtsir20:~# dmesg | tail -6
> [   40.753967] Bluetooth: RFCOMM socket layer initialized
> [   40.759277] Bluetooth: RFCOMM ver 1.11
> [   43.683766] mxc: set GPIO 9 to high trigger
> [   44.766186] mxc: switch GPIO 9 to low trigger
> [ 3120.825803] mxc: switch GPIO 9 to high trigger
> [ 3126.281689] mxc: switch GPIO 9 to low trigger
>
> But GPIO9 is defined as output not as IRQ
> and act as output so enable/disable an external device
> connected to it.
>
> Why its sets the interrupts?
>
Works as designed!
I enabled the LED for GPIO9 (/sys/class/led/green/gpio = 9, 
/sys/class/led/trigger = gpio)

sorry about the noise here.

Now I going to dump the registers - to see what if I can find the 
GPIO10/12 bug.