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>
index | next in thread | previous in thread | raw e-mail
On Fri, 24 Apr 2015 12:22:10 +0300
Daniel Braniss <danny@cs.huji.ac.il> wrote:
>
> > On Apr 24, 2015, at 11:16 AM, Milan Obuch <freebsd-arm@dino.sk>
> > wrote:
> >
> > 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 = “rfid,mfrc5”;
> >> spi-chipselect = <0>;
> >> reset {
> >> compatible = “pcd-reset”;
> >> gpios = <&gpio 22 2>;
> >> };
> >> };
> >>
> >> my mfrc5 driver is starting to work - i can load, open, ioctl,
> >> unload, but after much grepping, I can’t figure out how from
> >> inside the driver i can access the reset pin - which i have
> >> defined as gpio 22 ofwdump -aP
[ snip ]
> > Hello,
> >
> > I think following could help - I am forwarding what was given to me
> > in similar circumstances :)
> >
> > http://pastebin.com/4mbZFuv1 <http://pastebin.com/4mbZFuv1>;
>
> argh, is this for -stable or -current?
>
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
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150424113953.2d816a4c>