Date: Sat, 30 Oct 2010 15:18:54 +0200 From: Rafal Jaworowski <raj@semihalf.com> To: Milan Obuch <freebsd-arm@dino.sk> Cc: freebsd-arm@freebsd.org Subject: Re: Guruplug gpio Message-ID: <90B83E3E-C1CF-4233-8813-1C652ACEF252@semihalf.com> In-Reply-To: <201010300037.03374.freebsd-arm@dino.sk> References: <201010300037.03374.freebsd-arm@dino.sk>
next in thread | previous in thread | raw e-mail | index | archive | help
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=20
> are some of them accessible via u-snap connector and some of them are =
used to=20
> controll status LEDs.
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.
> there is some description in file bindings-gpio.txt, but I did not =
find=20
> something used in dts files, so I only guessed gpios could be defined =
the=20
> following way:
>=20
> GPIO: gpio@10100 =
=
=20
> {#gpio-cells =3D <3>;
> compatible =3D "mrvl,gpio";
> reg =3D <0x10100 0x20>;
> gpio-controller;
> interrupts =3D <35 36 37 38 39 40 41>;
> interrupt-parent =3D <&PIC>;
> gpios =3D
> <&GPIO 46 2 0x00000000 /* GPIO[46]: OUT */ =
=20=
> &GPIO 47 2 0x00000000 /* GPIO[47]: OUT */ =
=20=
> &GPIO 48 2 0x00000000 /* GPIO[48]: OUT */ =
=20=
> &GPIO 49 2 0x00000000 /* GPIO[49]: OUT */ =
=20=
>> ;
> };
The "gpios" property cannot be part of the GPIO controller node -- it =
belongs to the node, which is a consumer of GPIO lines which belong to =
some GPIO controller. For example, when PCI IRQs are routed through GPIO =
lines: it is the PCI node that should contain the "gpios" prop =
referencing their parent GPIO controller and specifying which GPIO lines =
are used and how they are configured (polarity, trigger and other =
attributes).
Rafal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?90B83E3E-C1CF-4233-8813-1C652ACEF252>