From: Pavel Machek <pavel@denx.de>
To: atull@opensource.altera.com
Cc: gregkh@linuxfoundation.org, jgunthorpe@obsidianresearch.com,
hpa@zytor.com, monstr@monstr.eu, michal.simek@xilinx.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
pantelis.antoniou@konsulko.com, robh+dt@kernel.org,
grant.likely@linaro.org, broonie@kernel.org, philip@balister.org,
rubini@gnudd.com, s.trumtrar@pengutronix.de,
jason@lakedaemon.net, kyle.teske@ni.com, nico@linaro.org,
balbi@ti.com, m.chehab@samsung.com, davidb@codeaurora.org,
rob@landley.net, davem@davemloft.net, cesarb@cesarb.net,
sameo@linux.intel.com, akpm@linux-foundation.org,
linus.walleij@linaro.org, delicious.quinoa@gmail.com,
dinguyen@opensource.altera.com, yvanderv@opensource.altera.com
Subject: Re: [PATCH 0/3] Yet another stab at a fpga framework
Date: Sun, 7 Sep 2014 20:57:00 +0200 [thread overview]
Message-ID: <20140907185700.GA26553@amd> (raw)
In-Reply-To: <1406932118-13885-1-git-send-email-atull@opensource.altera.com>
Hi!
> [resend with fixed email settings]
>
> The idea of the framework is to provide consistent ways of
> programming raw images into FPGA's.
>
> Programming from device tree overlays is supported.
>
> The core (fpga-mgr.c) does not include a userspace interface
> and just exports kernel functions.
>
> This approach separates the core from the interfaces.
>
> Each interface can be enabled or disabled in the defconfig.
> In some production contexts, interfaces that might be used
> during development can be disabled.
>
> The core exports kernel functions to:
> * write the fpga from a buffer or using the firmware layer
> * get fpga status
> * find a particular fpga manager from a device tree phandle
> * register/unregister lower level fpga drivers.
>
> The bus allows us to:
> * program fpga from a device tree overlay using firmware.
> * automatically reload firmware and reprogram fpga during resume.
>
> The sysfs interface:
> * read only, get the name and status of fpga manager.
>
> I have a configfs interface patch which I haven't included,
> adds configfs as a separate file.
Thanks for the patches... is there new version? Is that corresponding
socfpga code?
I'd like to configure fpga with .rbf file on board similar to SocKit.
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2014-09-07 18:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 22:28 [PATCH 0/3] Yet another stab at a fpga framework atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx
2014-08-01 22:28 ` [PATCH 1/3] fpga manager framework core atull
2014-08-02 0:15 ` Pavel Machek
2014-08-05 18:11 ` Alan Tull
[not found] ` <1406932118-13885-2-git-send-email-atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
2014-08-02 0:18 ` Pavel Machek
2014-08-05 20:05 ` Alan Tull
2014-08-09 14:50 ` Pavel Machek
2014-08-09 15:49 ` Greg Kroah-Hartman
[not found] ` <1406932118-13885-1-git-send-email-atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
2014-08-01 22:28 ` [PATCH 2/3] fpga bus driver atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx
[not found] ` <1406932118-13885-3-git-send-email-atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
2014-08-02 0:23 ` Pavel Machek
2014-08-05 17:11 ` Alan Tull
2014-08-05 18:21 ` Pantelis Antoniou
2014-08-01 22:28 ` [PATCH 3/3] fpga sysfs interface atull
[not found] ` <1406932118-13885-4-git-send-email-atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
2014-08-02 0:25 ` Pavel Machek
2014-08-05 18:18 ` [PATCH 0/3] Yet another stab at a fpga framework Pantelis Antoniou
2014-09-07 18:57 ` Pavel Machek [this message]
2014-09-08 21:00 ` atull
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=20140907185700.GA26553@amd \
--to=pavel@denx.de \
--cc=akpm@linux-foundation.org \
--cc=atull@opensource.altera.com \
--cc=balbi@ti.com \
--cc=broonie@kernel.org \
--cc=cesarb@cesarb.net \
--cc=davem@davemloft.net \
--cc=davidb@codeaurora.org \
--cc=delicious.quinoa@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@opensource.altera.com \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=kyle.teske@ni.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=nico@linaro.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=philip@balister.org \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=rubini@gnudd.com \
--cc=s.trumtrar@pengutronix.de \
--cc=sameo@linux.intel.com \
--cc=yvanderv@opensource.altera.com \
/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).