Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 Jan 2013 10:28:14 +0100
From:      Damjan Marion <damjan.marion@gmail.com>
To:        Emmanuel Vadot <elbarto@megadrive.org>, Oleksandr Tymoshenko <gonzo@bluezbox.com>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: Beaglebone and GPIO
Message-ID:  <22039243-8515-4245-97D1-48C29CB04F00@gmail.com>
In-Reply-To: <20130128063436.707fb62d79767d2d8ce0542a@megadrive.org>
References:  <20130128044511.86a3d715b11c3346884a7056@megadrive.org> <20130128063436.707fb62d79767d2d8ce0542a@megadrive.org>

next in thread | previous in thread | raw e-mail | index | archive | help

On Jan 28, 2013, at 6:34 AM, Emmanuel Vadot <elbarto@megadrive.org> =
wrote:

> On Mon, 28 Jan 2013 04:45:11 +0100
> Emmanuel Vadot <elbarto@megadrive.org> wrote:
>=20
>>=20
>> Hello,
>>=20
>> 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).
>>=20
>> 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).
>>=20
>> 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".
>>=20
>> Cheers,
>=20
> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22039243-8515-4245-97D1-48C29CB04F00>