From 5d64e8a26388e2abbf6a6585d17392d6e944ae7b Mon Sep 17 00:00:00 2001
From: Daniel Baumann <daniel.baumann@progress-linux.org>
Date: Sat, 1 Jul 2023 00:38:51 +0200
Subject: Merging upstream version 2.5.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
---
 Documentation/nvme-ocp-device-capability-log.txt | 42 ++++++++++++++++++++++++
 1 file changed, 42 insertions(+)
 create mode 100644 Documentation/nvme-ocp-device-capability-log.txt

(limited to 'Documentation/nvme-ocp-device-capability-log.txt')

diff --git a/Documentation/nvme-ocp-device-capability-log.txt b/Documentation/nvme-ocp-device-capability-log.txt
new file mode 100644
index 0000000..7789531
--- /dev/null
+++ b/Documentation/nvme-ocp-device-capability-log.txt
@@ -0,0 +1,42 @@
+nvme-ocp-device-capability-log(1)
+=================================
+
+NAME
+----
+nvme-ocp-device-capability-log - Retrieves OCP Device Capability Log Page
+
+SYNOPSIS
+--------
+[verse]
+'nvme ocp device-capability-log' <device> [--output-format=<fmt> | -o <fmt>]
+
+DESCRIPTION
+-----------
+For the NVMe device given, retrieves OCP Device Capability Log Page
+
+The <device> parameter is mandatory and may be either the NVMe character
+device (ex: /dev/nvme0) or block device (ex: /dev/nvme0n1).
+
+This will only work on OCP compliant devices supporting this feature.
+Results for any other device are undefined.
+
+On success it returns 0, error code otherwise.
+
+OPTIONS
+-------
+-o <format>::
+--output-format=<format>::
+	Set the reporting format to 'normal' or 'json' or 'binary'. 
+	Only one output format can be used at a time. The default is normal.
+
+EXAMPLES
+--------
+* Has the program issue a device-capability-log command to retrieve the 0xC4 log page.
++
+------------
+# nvme ocp device-capability-log /dev/nvme0 -o normal
+------------
+
+NVME
+----
+Part of the nvme-user suite.
-- 
cgit v1.2.3