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,
rdunlap@infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, pantelis.antoniou@konsulko.com,
robh+dt@kernel.org, grant.likely@linaro.org,
iws@ovro.caltech.edu, linux-doc@vger.kernel.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,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devel@driverdev.osuosl.org, Petr Cvek <petr.cvek@tul.cz>,
delicious.quinoa@gmail.com, dinguyen@opensource.altera.com,
yvande
Subject: Re: [PATCH v9 2/7] staging: usage documentation for simple fpga bus
Date: Thu, 23 Jul 2015 08:43:39 +0200 [thread overview]
Message-ID: <20150723064338.GB23318@amd> (raw)
In-Reply-To: <1437148277-5405-3-git-send-email-atull@opensource.altera.com>
On Fri 2015-07-17 10:51:12, atull@opensource.altera.com wrote:
> From: Alan Tull <atull@opensource.altera.com>
>
> Add a document spelling out usage of the simple fpga bus.
> +The DT overlay includes bindings (documented in bindings/simple-fpga-bus.txt)
> +that specify:
> + * Which fpga manager to use
fpga->FPGA, globally.
> + * Which image file to load
> + * Flags indicating whether this this image is for full reconfiguration or
> + partial.
> + * a list of resets that should be released. These enable the FPGA bridges.
> + * child nodes specifying the devices that will be added with appropriate
> + compatible strings, etc.
Either all entries in the list should start with big letter or none
should. Also . at end of line should be consistent.
> + Sequence
> + --------
> + 1. Load the DT overlay. One convenient way to do that is to use Pantelis'
> + handy configfs interface (more below).
Reader has no chance to know what Pantelis' configfs interface is, and
there's nothing below.
> + 2. The simple FPGA bus gets probed and will do the following:
> + a. call the fpga manager core to program the FPGA
> + b. release the FPGA bridges
> + c. call of_platform_populate resulting in device drivers getting probed.
> +
--
(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:[~2015-07-23 6:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 15:51 [PATCH v9 0/7] FPGA Manager Framework and Simple FPGA Bus atull
2015-07-17 15:51 ` [PATCH v9 1/7] staging: usage documentation for FPGA manager core atull
2015-07-23 6:38 ` Pavel Machek
2015-07-17 15:51 ` [PATCH v9 2/7] staging: usage documentation for simple fpga bus atull
2015-07-23 6:43 ` Pavel Machek [this message]
2015-07-17 15:51 ` [PATCH v9 3/7] staging: add bindings document " atull
2015-07-17 19:49 ` Steffen Trumtrar
2015-07-17 21:21 ` Jason Gunthorpe
2015-07-17 21:22 ` atull
2015-07-23 7:31 ` Steffen Trumtrar
2015-07-23 6:46 ` Pavel Machek
2015-07-17 15:51 ` [PATCH v9 4/7] staging: fpga manager: add sysfs interface document atull
2015-07-24 8:18 ` Pavel Machek
2015-07-24 12:39 ` atull
2015-07-24 12:43 ` Pavel Machek
2015-07-17 15:51 ` [PATCH v9 5/7] staging: fpga manager core atull
2015-07-17 17:27 ` Randy Dunlap
2015-07-17 18:25 ` atull
2015-07-22 21:47 ` Moritz Fischer
2015-07-23 16:28 ` atull
2015-07-17 15:51 ` [PATCH v9 6/7] staging: add simple-fpga-bus atull
2015-07-23 21:55 ` Moritz Fischer
2015-07-23 22:15 ` Jason Gunthorpe
2015-07-24 3:42 ` atull
2015-07-17 15:51 ` [PATCH v9 7/7] staging: fpga manager: add driver for socfpga fpga manager atull
2015-07-17 21:06 ` Moritz Fischer
2015-07-17 21:42 ` atull
2015-07-17 17:25 ` [PATCH v9 0/7] FPGA Manager Framework and Simple FPGA Bus Jason Gunthorpe
2015-07-17 18:09 ` atull
2015-07-22 20:32 ` atull
2015-07-22 21:11 ` Jason Gunthorpe
2015-07-22 21:39 ` atull
2015-07-23 4:12 ` Greg KH
2015-07-23 16:37 ` 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=20150723064338.GB23318@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=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@opensource.altera.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=iws@ovro.caltech.edu \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=kyle.teske@ni.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=nico@linaro.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=pawel.moll@arm.com \
--cc=petr.cvek@tul.cz \
--cc=philip@balister.org \
--cc=rdunlap@infradead.org \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=rubini@gnudd.com \
--cc=s.trumtrar@pengutronix.de \
--cc=sameo@linux.intel.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).