From: <atull@opensource.altera.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Moritz Fischer <moritz.fischer@ettus.com>,
Josh Cartwright <joshc@ni.com>,
gregkh@linuxfoundation.org, monstr@monstr.eu,
michal.simek@xilinx.com, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, pantelis.antoniou@konsulko.com,
delicious.quinoa@gmail.com, dinguyen@opensource.altera.com,
Alan Tull <atull@opensource.altera.com>
Subject: [PATCH v14 3/7] add sysfs document for fpga bridge class
Date: Thu, 10 Dec 2015 17:37:05 -0600 [thread overview]
Message-ID: <1449790629-5517-4-git-send-email-atull@opensource.altera.com> (raw)
In-Reply-To: <1449790629-5517-1-git-send-email-atull@opensource.altera.com>
From: Alan Tull <atull@opensource.altera.com>
Add documentation for new FPGA bridge class's sysfs interface.
Signed-off-by: Alan Tull <atull@opensource.altera.com>
---
Documentation/ABI/testing/sysfs-class-fpga-bridge | 11 +++++++++++
1 file changed, 11 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-class-fpga-bridge
diff --git a/Documentation/ABI/testing/sysfs-class-fpga-bridge b/Documentation/ABI/testing/sysfs-class-fpga-bridge
new file mode 100644
index 0000000..e45d952
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-class-fpga-bridge
@@ -0,0 +1,11 @@
+What: /sys/class/fpga_bridge/<bridge>/name
+Date: December 2015
+KernelVersion: 4.4
+Contact: Alan Tull <atull@opensource.altera.com>
+Description: Name of low level FPGA bridge driver.
+
+What: /sys/class/fpga_bridge/<bridge>/state
+Date: December 2015
+KernelVersion: 4.4
+Contact: Alan Tull <atull@opensource.altera.com>
+Description: Show bridge state as "enabled" or "disabled"
--
1.7.9.5
next prev parent reply other threads:[~2015-12-10 23:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 23:37 [PATCH v14 0/7] fpga area and fpga bridge framework atull
2015-12-10 23:37 ` [PATCH v14 1/7] fpga: add usage documentation for fpga area atull
2015-12-11 15:05 ` Rob Herring
2015-12-11 18:33 ` atull
2015-12-11 19:18 ` Rob Herring
2015-12-10 23:37 ` [PATCH v14 2/7] fpga: add bindings document " atull
2015-12-11 14:34 ` Rob Herring
2015-12-10 23:37 ` atull [this message]
2015-12-10 23:37 ` [PATCH v14 4/7] ARM: socfpga: add bindings document for fpga bridge drivers atull
2015-12-10 23:37 ` [PATCH v14 5/7] fpga: add fpga bridge framework atull
2015-12-10 23:37 ` [PATCH v14 6/7] fpga: fpga-area: support device tree control for FPGA programming atull
2015-12-10 23:37 ` [PATCH v14 7/7] ARM: socfpga: fpga bridge driver support atull
2015-12-14 17:16 ` [PATCH v14 0/7] fpga area and fpga bridge framework Moritz Fischer
2015-12-15 1:56 ` Alan Tull
2015-12-15 18:15 ` Moritz Fischer
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=1449790629-5517-4-git-send-email-atull@opensource.altera.com \
--to=atull@opensource.altera.com \
--cc=corbet@lwn.net \
--cc=delicious.quinoa@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@opensource.altera.com \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=joshc@ni.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=moritz.fischer@ettus.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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).