Date: Thu, 19 Jul 2012 18:40:12 +0200 From: Damjan Marion <dmarion@freebsd.org> To: David Kalliecharan <davidkallie@gmail.com> Cc: freebsd-arm@freebsd.org Subject: Re: BeagleBone GPIO Message-ID: <80CCC0AE-ABC7-45B3-A1FE-78376D064A6C@freebsd.org> In-Reply-To: <CABHk%2BD=o70yzm8YtQj5660FodY_w1DAsTyCxakuU_41_p9rLQg@mail.gmail.com> References: <CABHk%2BD=o70yzm8YtQj5660FodY_w1DAsTyCxakuU_41_p9rLQg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi David, GPIO driver works for 1st 32 GPIOs, and gpioctl is right tool but you=20 cannot list GPIOs, you can just toggle them. You can see list of gpios in sys/arm/ti/am335x/am335x_scm_padconf.c and might be that you will need to change settings in = sys/boot/fdt/dts/beaglebone.dts. For a proper support gpioctl tool needs complete rewrite, as it = currently=20 assumes that there is no more that 32 gpios available. Cheers, Damjan On Jul 19, 2012, at 6:29 PM, David Kalliecharan <davidkallie@gmail.com> = wrote: > Hi Damjan, >=20 > I am attempting to do some work on the BeagleBone and am curious about > the GPIO driver, I was directed to you by Tim Kientzle, who has helped > me get a working system and am going to attempt to help him in any way > I can. I attempted to list off the available pins using the gpioctl > command and got the error: >=20 > # gpioctl -f /dev/gpioc0 -l > ioctl(GPIOGET): Invalid argument >=20 > Not sure if I am using the correct userland tool, as Tim informed me > that there was a tool to use and a driver you were working on and had > assumed it to be 'gpioctl'. If I can help with testing or anything let > me know (I am trying to get my feet wet with this stuff), again thanks > for taking the time to help, I really appreciate it! >=20 > Cheers, >=20 > Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80CCC0AE-ABC7-45B3-A1FE-78376D064A6C>