Date: Sat, 30 Oct 2010 15:17:51 -0700 From: Oleksandr Tymoshenko <gonzo@bluezbox.com> To: Milan Obuch <freebsd-arm@dino.sk> Cc: freebsd-arm@freebsd.org Subject: Re: Guruplug gpio Message-ID: <04048D7D-DF99-4CC6-A4D0-C59C6BBE0DF8@bluezbox.com> In-Reply-To: <201010301900.36922.freebsd-arm@dino.sk> References: <201010300037.03374.freebsd-arm@dino.sk> <90B83E3E-C1CF-4233-8813-1C652ACEF252@semihalf.com> <201010301900.36922.freebsd-arm@dino.sk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2010-10-30, at 10:00 AM, Milan Obuch wrote:
> On Saturday 30 October 2010 15:18:54 Rafal Jaworowski wrote:
>> On 2010-10-30, at 00:37, Milan Obuch wrote:
>>> Hi,
>>>=20
>>> after solving mge1 problem I decided to work a bit with Guruplug's =
gpio.
>>> There are some of them accessible via u-snap connector and some of =
them
>>> are used to controll status LEDs.
>>=20
>> As mentioned in another email, Marvell GPIO driver does not get hooks =
for
>> the new framework, so this needs to be provided first before you'd be =
able
>> to controll LEDs from userspace etc.
>>=20
>=20
> I see. I am going to investigate how this could be done. I did some =
work with=20
> GPIO based on some older work, so I just need to check the =
infrastructure for=20
> GPIO (gpiobus, gpio properties etc).
Bear in mind that GPIO framework is work ing progress and its =
abilities=20
are very limited at the moment. Feel free to send patches or feature =
requests=20
--=20
gonzo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?04048D7D-DF99-4CC6-A4D0-C59C6BBE0DF8>