From owner-freebsd-arm@FreeBSD.ORG  Fri Apr 24 08:00:57 2015
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: 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 7B149774
 for <arm@freebsd.org>; Fri, 24 Apr 2015 08:00:57 +0000 (UTC)
Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 33343159A
 for <arm@freebsd.org>; Fri, 24 Apr 2015 08:00:56 +0000 (UTC)
Received: from th-04.cs.huji.ac.il ([132.65.80.125])
 by kabab.cs.huji.ac.il with esmtp id 1YlYXJ-000HL4-L5
 for arm@freebsd.org; Fri, 24 Apr 2015 11:00:33 +0300
From: Daniel Braniss <danny@cs.huji.ac.il>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: FDT help
Message-Id: <80F17668-BEF0-42BD-9243-AE41ACAF255E@cs.huji.ac.il>
Date: Fri, 24 Apr 2015 11:00:33 +0300
To: arm@freebsd.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
X-Mailer: Apple Mail (2.2098)
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:00:57 -0000

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>;
			};
	};

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

# 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

thanks,
	danny