For the NVMe device given, sends an identify primary Controller caps command and provides the result and returned structure\&.
.sp
The <device> parameter is mandatory and may be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1)\&.
.sp
On success, the structure may be returned in one of several ways depending on the option flags; the structure may be parsed by the program or the raw buffer may be printed to stdout\&.
.SH"OPTIONS"
.PP
\-o <format>, \-\-output\-format=<format>
.RS4
Set the reporting format to
\fInormal\fR,
\fIjson\fR, or
\fIbinary\fR\&. Only one output format can be used at a time\&.
.RE
.PP
\-H, \-\-human\-readable
.RS4
This option will parse and format many of the bit fields into human\-readable formats\&.
.RE
.SH"EXAMPLES"
.sp
.RS4
.ien\{\
\h'-04'\(bu\h'+03'\c
.\}
.el\{\
.sp-1
.IP\(bu2.3
.\}
Get Primary Ctrl Caps of the device in default format
.sp
.ifn\{\
.RS4
.\}
.nf
# nvme primary\-ctrl\-caps /dev/nvme0
.fi
.ifn\{\
.RE
.\}
.RE
.sp
.RS4
.ien\{\
\h'-04'\(bu\h'+03'\c
.\}
.el\{\
.sp-1
.IP\(bu2.3
.\}
Has the program interpret the returned buffer and display the known fields in a human readable format: