Date: Fri, 6 Sep 2013 13:42:31 -0600 From: Warner Losh <imp@bsdimp.com> To: Luiz Otavio O Souza <lists.br@gmail.com> Cc: freebsd-embedded <freebsd-embedded@freebsd.org> Subject: Re: GPIO hint meanings Message-ID: <097A9AFF-D291-4D9F-92CC-12E5E453F7C7@bsdimp.com> In-Reply-To: <CAB=2f8yEx4UPc1QeHP%2BbJCDadDRvBJyvTkPjztVv4VG5uoULQw@mail.gmail.com> References: <1378488150.1637.5.camel@localhost> <CAB=2f8yEx4UPc1QeHP%2BbJCDadDRvBJyvTkPjztVv4VG5uoULQw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 6, 2013, at 12:31 PM, Luiz Otavio O Souza wrote: > On 6 September 2013 14:22, Sean Bruno <sean_bruno@yahoo.com> wrote: >=20 >> I think I have a fairly firm grasp on what some of the mips/gpio = hints >> mean, e.g.: >>=20 >> hint.gpio.0.pinmask >> hint.gpioled.0.at >> hint.gpioled.0.name >> hint.gpioled.0.pins >>=20 >> Fairly straightforward. >>=20 >> Now, what do these mean/do: >>=20 >> hint.gpio.0.function_set >> hint.gpio.0.function_clear >>=20 >> ? >>=20 >> Sean >>=20 >> p.s. I think I'll take this and thrash together a gpioled(4) and = gpio(4) >> man page if I can understand better. >>=20 >=20 >=20 > Hi Sean, >=20 > Some of the GPIO pins on this SoC family (ar724x, ar71xx and ar9xxx) = can be > set between GPIO and an alternate function. So adding a pin to = function_set > enables this alternate function and the function_clear disables it > (sometimes the bootloader doesn't initialize properly those pins). >=20 > Each SoC has its own set of pins and functions. >=20 > For ar71xx the pins 0 and 1 can be used as additional SPI chip select > outputs, pins 9 and 10 are used for UART and there are also reserved = pins > for a SLIC/I2S interface. We really need a pinmux/pinctl type interface for this which is standard = across drivers/platforms. Warner=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?097A9AFF-D291-4D9F-92CC-12E5E453F7C7>