From owner-freebsd-arm@FreeBSD.ORG Fri Apr 24 09:22:23 2015 Return-Path: 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 5DD8161C for ; Fri, 24 Apr 2015 09:22:23 +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 103721E4E for ; Fri, 24 Apr 2015 09:22:22 +0000 (UTC) Received: from th-04.cs.huji.ac.il ([132.65.80.125]) by kabab.cs.huji.ac.il with esmtp id 1YlZoI-000Jjs-Iz; Fri, 24 Apr 2015 12:22:10 +0300 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) Subject: Re: FDT help From: Daniel Braniss In-Reply-To: <20150424101610.469ba9bc@zeta.dino.sk> Date: Fri, 24 Apr 2015 12:22:10 +0300 Cc: freebsd-arm@freebsd.org Message-Id: <90F87E7F-1A16-46EF-8996-5519502A5B76@cs.huji.ac.il> References: <80F17668-BEF0-42BD-9243-AE41ACAF255E@cs.huji.ac.il> <20150424101610.469ba9bc@zeta.dino.sk> To: Milan Obuch X-Mailer: Apple Mail (2.2098) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Apr 2015 09:22:23 -0000 > On Apr 24, 2015, at 11:16 AM, Milan Obuch wrote: >=20 > On Fri, 24 Apr 2015 11:00:33 +0300 > Daniel Braniss 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 >>=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 >>=20 >=20 > Hello, >=20 > I think following could help - I am forwarding what was given to me in > similar circumstances :) >=20 > http://pastebin.com/4mbZFuv1 argh, is this for -stable or -current? thanks, danny >=20 > Regards, > Milan > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"