Debian Codegraph @

doc/man/nvme_mi_message_type.2

raw
1 .TH "libnvme" 9 "enum nvme_mi_message_type" "November 2025" "API Manual" LINUX
2 .SH NAME
3 enum nvme_mi_message_type \- NVMe-MI message type field.
4 .SH SYNOPSIS
5 enum nvme_mi_message_type {
6 .br
7 .BI " NVME_MI_MT_CONTROL"
8 ,
9 .br
10 .br
11 .BI " NVME_MI_MT_MI"
12 ,
13 .br
14 .br
15 .BI " NVME_MI_MT_ADMIN"
16 ,
17 .br
18 .br
19 .BI " NVME_MI_MT_PCIE"
20 ,
21 .br
22 .br
23 .BI " NVME_MI_MT_AE"
24
25 };
26 .SH Constants
27 .IP "NVME_MI_MT_CONTROL" 12
28 NVME-MI Control Primitive
29 .IP "NVME_MI_MT_MI" 12
30 NVMe-MI command
31 .IP "NVME_MI_MT_ADMIN" 12
32 NVMe Admin command
33 .IP "NVME_MI_MT_PCIE" 12
34 PCIe command
35 .IP "NVME_MI_MT_AE" 12
36 Asynchronous Event
37 .SH "Description"
38 Used as byte 1 of both request and response messages (NMIMT bits of NMP
39 byte). Not to be confused with the MCTP message type in byte 0.