[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130919111719.GA26246@amd.pavel.ucw.cz>
Date: Thu, 19 Sep 2013 13:17:19 +0200
From: Pavel Machek <pavel@...x.de>
To: Michal Simek <monstr@...str.eu>
Cc: Alan Tull <atull@...era.com>,
Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
Jason Cooper <jason@...edaemon.net>,
Michal Simek <michal.simek@...inx.com>,
linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Dinh Nguyen <dinguyen@...era.com>,
Philip Balister <philip@...ister.org>,
Alessandro Rubini <rubini@...dd.com>,
Mauro Carvalho Chehab <m.chehab@...sung.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Cesar Eduardo Barros <cesarb@...arb.net>,
Joe Perches <joe@...ches.com>,
"David S. Miller" <davem@...emloft.net>,
Stephen Warren <swarren@...dia.com>,
Arnd Bergmann <arnd@...db.de>,
David Brown <davidb@...eaurora.org>,
Dom Cobley <popcornmix@...il.com>
Subject: Re: [RFC PATCH] fpga: Introduce new fpga subsystem
Hi!
> > This code also creates a set of files under /sys for each separate fpga.
> > I.e. checking status by looking at /sys/class/fpga/fpag0/status. It
> > would be pretty small changes to control reseting the fpga by adding a
> > 'reset' file there also (added first to the framework, and an interface
> > into the low level fpga manager driver).
>
> Status is just there and for my zynq devcfg driver I do export some status
> bits.
>
> root@...alinux:~# cat /sys/class/fpga/fpga0/status
> partial_bitstream_status: 0
> prog_done_status: 1
> dbg_lock_status: 0
> seu_lock_status: 0
> aes_en_lock_status: 0
> aes_status: 0
> seu_status: 0
> spniden_status: 1
> spiden_status: 1
> niden_status: 1
> dbgen_status: 1
> dap_en_status: 7
This is single file? If so, it needs to be changed. Greg is rather
clear about that.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists