From: michal.simek@xilinx.com (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: FPGA manager user space interface
Date: Mon, 11 Jul 2016 14:20:15 +0200 [thread overview]
Message-ID: <57838EFF.50200@xilinx.com> (raw)
In-Reply-To: <5782BE1A.9090905@gmail.com>
Hi Florian,
I didn't follow all stuff regarding FPGA manager and I can't remember
the reasons against user interfaces. Alan probably knows.
Thanks,
Michal
On 10.7.2016 23:28, Florian Fainelli wrote:
> Hi all,
>
> I just wrote a FPGA manager driver for the TS-7300 board which features
> an Altera Cyclone II on board. While the finished solution is my case
> might be something like the MFD driver for the FPGA devices requesting
> the bitstream load and registering the different devices it exposes,
> during development it is nice to exercise the FPGA manager driver to
> load something:
>
> - a quick way is to add a pair of sysfs attributes to define the
> bitstream filename and to trigger the load
>
> - offer a more consistent and robust interface through e.g; a character
> device that you can write/read/poll to see the loading progress about
>
> - have the driver exposing FPGA peripherals be exposing an user space
> interface to trigger a (re)load/(re)/configuration, although that's
> really something that belongs in the FPGA manager it seems
>
> I am mostly curious if these were taken into account during the initial
> design and it is agreed upon that yes these are some of options and that
> userspace loading is just anecdotal we do not need any userspace
> interface, or if this is just missing and we want one? Either way, I
> don't mind submitting what I came up with for the TS-7300 board.
>
> Thanks!
> --
> Florian
>
next prev parent reply other threads:[~2016-07-11 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 21:28 FPGA manager user space interface Florian Fainelli
2016-07-11 12:20 ` Michal Simek [this message]
2016-07-11 16:59 ` atull
2016-07-11 17:38 ` Florian Fainelli
2016-07-12 15:15 ` atull
2016-07-12 22:03 ` Florian Fainelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57838EFF.50200@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).