From owner-freebsd-arm@FreeBSD.ORG  Fri Apr 24 08:16:21 2015
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D1931A33
 for <freebsd-arm@freebsd.org>; Fri, 24 Apr 2015 08:16:21 +0000 (UTC)
Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5478016F9
 for <freebsd-arm@freebsd.org>; Fri, 24 Apr 2015 08:16:20 +0000 (UTC)
Received: from zeta.dino.sk (fw1.dino.sk [84.245.95.252]) (AUTH: LOGIN milan)
 by mailhost.netlabit.sk with ESMTPA; Fri, 24 Apr 2015 10:16:10 +0200
 id 001A3CFE.5539FBCA.0001057C
Date: Fri, 24 Apr 2015 10:16:10 +0200
From: Milan Obuch <freebsd-arm@dino.sk>
To: freebsd-arm@freebsd.org
Subject: Re: FDT help
Message-ID: <20150424101610.469ba9bc@zeta.dino.sk>
In-Reply-To: <80F17668-BEF0-42BD-9243-AE41ACAF255E@cs.huji.ac.il>
References: <80F17668-BEF0-42BD-9243-AE41ACAF255E@cs.huji.ac.il>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; i386-portbld-freebsd10.1)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2015 08:16:21 -0000

On Fri, 24 Apr 2015 11:00:33 +0300
Daniel Braniss <danny@cs.huji.ac.il> wrote:

> Hi,
> I have this in my rpi.dts file:
> 	spi0 {
> 		rfid0 {
> 			compatible =3D =E2=80=9Crfid,mfrc5=E2=80=9D;
> 			spi-chipselect =3D <0>;
> 			reset {
> 				compatible =3D =E2=80=9Cpcd-reset=E2=80=9D;
> 				gpios =3D <&gpio 22 2>;
> 			};
> 	};
>=20
> my mfrc5 driver is starting to work - i can load, open, ioctl, unload,
> but after much grepping, I can=E2=80=99t figure out how from inside the
> driver i can access the reset pin - which i have defined as gpio 22
> ofwdump -aP
>=20
> # ofwdump -aP
>     ...
>     Node 0x13c4: spi0
>       compatible:
>         62 72 6f 61 64 63 6f 6d 2c 62 63 6d 32 38 33 35 2d 73 70 69=20
>         00 62 72 6f 61 64 63 6f 6d 2c 62 63 6d 32 37 30 38 2d 73 70=20
>         69 00=20
>       reg:
>         00 20 40 00 00 00 00 20=20
>       interrupts:
>         00 00 00 3e=20
>       interrupt-parent:
>         00 00 00 01=20
>       Node 0x143c: rfid0
>         compatible:
>           72 66 69 64 2c 6d 66 72 63 35 00=20
>           'rfid,mfrc5'
>         spi-chipselect:
>           00 00 00 00=20
>         Node 0x1470: reset
>           compatible:
>             70 63 64 2d 72 65 73 65 74 00=20
>             'pcd-reset'
>           gpios:
>             00 00 00 03 00 00 00 16 00 00 00 02=20
>=20
> thanks,
> 	danny
>

Hello,

I think following could help - I am forwarding what was given to me in
similar circumstances :)

http://pastebin.com/4mbZFuv1

Regards,
Milan