This commit adds the ABI definitions exposed to userspace for
the platform/mellanox/mlxbf-bootctl driver.

Reviewed-by: Vadim Pasternak <[email protected]>
Signed-off-by: Liming Sun <[email protected]>
---
v5->v6:
    Fixes for comments from Mark:
    - Changed to use device attributes (DEVICE_ATTR_xx) instead of
      driver attributes (DRIVER_ATTR_xx) for the exported sysfs
      attributes.
---
 .../ABI/testing/sysfs-platform-mellanox-bootctl    | 58 ++++++++++++++++++++++
 MAINTAINERS                                        |  1 +
 2 files changed, 59 insertions(+)
 create mode 100644 Documentation/ABI/testing/sysfs-platform-mellanox-bootctl

diff --git a/Documentation/ABI/testing/sysfs-platform-mellanox-bootctl 
b/Documentation/ABI/testing/sysfs-platform-mellanox-bootctl
new file mode 100644
index 0000000..b60a46e
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-platform-mellanox-bootctl
@@ -0,0 +1,58 @@
+What:          /sys/bus/platform/devices/MLNXBF04:00/driver/lifecycle_state
+Date:          Oct 2019
+KernelVersion: 5.4
+Contact:       "Liming Sun <[email protected]>"
+Description:
+               The Life-cycle state of the SoC, which could be one of the
+               following values.
+                 Production - Production state and can be updated to secure
+                 GA Secured - Secure chip and not able to change state
+                 GA Non-Secured - Non-Secure chip and not able to change state
+                 RMA - Return Merchandise Authorization
+
+What:          /sys/bus/platform/devices/MLNXBF04:00/driver/post_reset_wdog
+Date:          Oct 2019
+KernelVersion: 5.4
+Contact:       "Liming Sun <[email protected]>"
+Description:
+               The watchdog setting in seconds for the next booting. It's used
+               to reboot the chip and recover it to the old state if the new
+               boot partition fails.
+
+What:          /sys/bus/platform/devices/MLNXBF04:00/driver/reset_action
+Date:          Oct 2019
+KernelVersion: 5.4
+Contact:       "Liming Sun <[email protected]>"
+Description:
+               The source of the boot stream for the next reset. It could be
+               one of the following values.
+                 external - boot from external source (USB or PCIe)
+                 emmc - boot from the onchip eMMC
+                 emmc_legacy - boot from the onchip eMMC in legacy (slow) mode
+
+What:          /sys/bus/platform/devices/MLNXBF04:00/driver/second_reset_action
+Date:          Oct 2019
+KernelVersion: 5.4
+Contact:       "Liming Sun <[email protected]>"
+Description:
+               Update the source of the boot stream after next reset. It could
+               be one of the following values and will be applied after next
+               reset.
+                 external - boot from external source (USB or PCIe)
+                 emmc - boot from the onchip eMMC
+                 emmc_legacy - boot from the onchip eMMC in legacy (slow) mode
+                 swap_emmc - swap the primary / secondary boot partition
+                 none - cancel the action
+
+What:          
/sys/bus/platform/devices/MLNXBF04:00/driver/secure_boot_fuse_state
+Date:          Oct 2019
+KernelVersion: 5.4
+Contact:       "Liming Sun <[email protected]>"
+Description:
+               The state of eFuse versions with the following values.
+                 InUse - burnt, valid and currently in use
+                 Used - burnt and valid
+                 Free - not burnt and free to use
+                 Skipped - not burnt but not free (skipped)
+                 Wasted - burnt and invalid
+                 Invalid - not burnt but marked as valid (error state).
diff --git a/MAINTAINERS b/MAINTAINERS
index 55199ef..c2ff283 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10435,6 +10435,7 @@ M:      Darren Hart <[email protected]>
 M:     Vadim Pasternak <[email protected]>
 L:     [email protected]
 S:     Supported
+F:     Documentation/ABI/testing/sysfs-platform-mellanox-bootctl
 F:     drivers/platform/mellanox/
 F:     include/linux/platform_data/mlxreg.h
 
-- 
1.8.3.1

Reply via email to