From: David Koltak <david.kol...@linux.intel.com>

commit 800553eb887b2477bed3693e931c6aadf484eefb from
https://github.com/altera-opensource/linux-socfpga.git

Documentation showing the proper device tree node
and binding for the Intel Remote System Update (RSU)
driver for Stratix 10 SoC FPGAs.

Signed-off-by: David Koltak <david.kol...@linux.intel.com>
Signed-off-by: Meng Li <meng...@windriver.com>
---
 .../bindings/firmware/intel,stratix10-rsu.txt      | 28 ++++++++++++++++++++++
 1 file changed, 28 insertions(+)
 create mode 100644 
Documentation/devicetree/bindings/firmware/intel,stratix10-rsu.txt

diff --git a/Documentation/devicetree/bindings/firmware/intel,stratix10-rsu.txt 
b/Documentation/devicetree/bindings/firmware/intel,stratix10-rsu.txt
new file mode 100644
index 0000000..9df6f89
--- /dev/null
+++ b/Documentation/devicetree/bindings/firmware/intel,stratix10-rsu.txt
@@ -0,0 +1,28 @@
+Intel Remote System Update (RSU) for Stratix10 SoC FPGAs
+============================================
+The Intel Remote System Update (RSU) driver exposes interfaces
+accessed through the Intel Service Layer to user space via SysFS
+device attribute nodes. The RSU interfaces report/control some of
+the optional RSU features of the Stratix 10 SoC FPGA.
+
+The RSU feature provides a way for customers to update the boot
+configuration of a Stratix 10 SoC device with significantly reduced
+risk of corrupting the bitstream storage and bricking the system.
+
+Required properties:
+-------------------
+The intel-rsu node has the following mandatory properties and must be located
+under the firmware/svc node.
+
+- compatible: "intel,stratix10-rsu"
+
+Example:
+-------
+
+       firmware {
+               svc {
+                       rsu {
+                               compatible = "intel,stratix10-rsu";
+                       };
+               };
+       };
-- 
2.7.4

-- 
_______________________________________________
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Reply via email to