From owner-freebsd-arm@FreeBSD.ORG  Fri Apr 24 09:39:58 2015
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 104D594A
 for <freebsd-arm@freebsd.org>; Fri, 24 Apr 2015 09:39:58 +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 807C91F7B
 for <freebsd-arm@freebsd.org>; Fri, 24 Apr 2015 09:39:56 +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 11:39:54 +0200
 id 001A3D18.553A0F6A.00014614
Date: Fri, 24 Apr 2015 11:39:53 +0200
From: Milan Obuch <freebsd-arm@dino.sk>
To: Daniel Braniss <danny@cs.huji.ac.il>
Cc: freebsd-arm@freebsd.org
Subject: Re: FDT help
Message-ID: <20150424113953.2d816a4c@zeta.dino.sk>
In-Reply-To: <90F87E7F-1A16-46EF-8996-5519502A5B76@cs.huji.ac.il>
References: <80F17668-BEF0-42BD-9243-AE41ACAF255E@cs.huji.ac.il>
 <20150424101610.469ba9bc@zeta.dino.sk>
 <90F87E7F-1A16-46EF-8996-5519502A5B76@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 09:39:58 -0000

On Fri, 24 Apr 2015 12:22:10 +0300
Daniel Braniss <danny@cs.huji.ac.il> wrote:

>=20
> > On Apr 24, 2015, at 11:16 AM, Milan Obuch <freebsd-arm@dino.sk>
> > wrote:
> >=20
> > On Fri, 24 Apr 2015 11:00:33 +0300
> > Daniel Braniss <danny@cs.huji.ac.il> wrote:
> >=20
> >> 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

[ snip ]

> > Hello,
> >=20
> > I think following could help - I am forwarding what was given to me
> > in similar circumstances :)
> >=20
> > http://pastebin.com/4mbZFuv1 <http://pastebin.com/4mbZFuv1>
>=20
> argh, is this for -stable or -current?
>=20

Well, I am not sure - maybe -current. I used it just as an inspiration,
basically took the '+' prefixed lines as a raw first version of what I
needed then to do - parse FDT blob and do what was necessary with GPIO
pin defined.

Regards,
Milan