/openbmc/u-boot/doc/ |
H A D | README.nvme | 6 What is NVMe 9 NVM Express (NVMe) is a register level interface that allows host software to 21 memory that is formatted into logical blocks. An NVMe namespace is equivalent 26 There is an NVMe uclass driver (driver name "nvme"), an NVMe host controller 27 driver (driver name "nvme") and an NVMe namespace block driver (driver name 28 "nvme-blk"). The host controller driver is supposed to probe the hardware and 31 is triggered by the NVMe uclass driver and the actual work is done in the NVMe 36 It only support basic block read/write functions in the NVMe driver. 40 CONFIG_NVME Enable NVMe device support 41 CONFIG_CMD_NVME Enable basic NVMe commands [all …]
|
/openbmc/qemu/docs/system/devices/ |
H A D | nvme.rst | 2 NVMe Emulation 5 QEMU provides NVMe emulation through the ``nvme``, ``nvme-ns`` and 6 ``nvme-subsys`` devices. 10 * `Adding NVMe Devices`_, `additional namespaces`_ and `NVM subsystems`_. 15 Adding NVMe Devices 21 The QEMU emulated NVMe controller implements version 1.4 of the NVM Express 29 The simplest way to attach an NVMe controller on the QEMU PCI bus is to add the 35 -device nvme,serial=deadbeef,drive=nvm 37 There are a number of optional general parameters for the ``nvme`` device. Some 38 are mentioned here, but see ``-device nvme,help`` to list all possible [all …]
|
/openbmc/u-boot/cmd/ |
H A D | nvme.c | 10 #include <nvme.h> 44 nvme, 8, 1, do_nvme, 46 "scan - scan NVMe devices\n" 47 "nvme detail - show details of current NVMe device\n" 48 "nvme info - show all available NVMe devices\n" 49 "nvme device [dev] - show or set current NVMe device\n" 50 "nvme part [dev] - print partition table of one or all NVMe devices\n" 51 "nvme read addr blk# cnt - read `cnt' blocks starting at block\n" 53 "nvme write addr blk# cnt - write `cnt' blocks starting at block\n"
|
/openbmc/docs/designs/ |
H A D | nvmemi-over-smbus.md | 1 # NVMe-MI over SMBus 9 Currently, OpenBMC does not support NVMe drive information. NVMe-MI 10 specification defines a command that can read the NVMe drive information via 11 SMBus directly. The NVMe drive can provide its information or status, like 13 monitor NVMe drives so appropriate action can be taken. 17 NVMe-MI specification defines a command called 18 `NVM Express Basic Management Command` that can read the NVMe drives information 22 For our purpose is retrieve NVMe drives information, therefore, using NVM 23 Express Basic Management Command where describe in NVMe-MI specification to 24 communicate with NVMe drives. According to different platforms, temperature [all …]
|
/openbmc/qemu/tests/qtest/ |
H A D | nvme-test.c | 2 * QTest testcase for NVMe 16 #include "block/nvme.h" 27 QNvme *nvme = obj; in nvme_get_driver() local 30 return &nvme->dev; in nvme_get_driver() 33 fprintf(stderr, "%s not present in nvme\n", interface); in nvme_get_driver() 39 QNvme *nvme = g_new0(QNvme, 1); in nvme_create() local 42 qpci_device_init(&nvme->dev, bus, addr); in nvme_create() 43 nvme->obj.get_driver = nvme_get_driver; in nvme_create() 45 return &nvme->obj; in nvme_create() 52 QNvme *nvme = obj; in nvmetest_oob_cmb_test() local [all …]
|
/openbmc/openbmc/meta-facebook/meta-bletchley/recipes-phosphor/sensors/ |
H A D | phosphor-nvme_%.bbappend | 6 file://nvme-json-rewrite \ 7 file://nvme-json-rewrite.conf \ 15 install -m 0755 ${UNPACKDIR}/nvme-json-rewrite ${D}${libexecdir}/${PN}/ 17 install -d ${D}${sysconfdir}/nvme 18 install -m 0644 -D ${UNPACKDIR}/nvme_config.json ${D}${sysconfdir}/nvme 22 nvme-json-rewrite.conf:xyz.openbmc_project.nvme.manager.service.d/nvme-json-rewrite.conf \
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-bsp/nvme-cli/ |
H A D | nvme-cli_2.12.bb | 1 SUMMARY = "NVMe management command line interface" 2 HOMEPAGE = "https://github.com/linux-nvme/nvme-cli" 11 SRC_URI = "git://github.com/linux-nvme/nvme-cli.git;branch=master;protocol=https" 19 ${sbindir}/nvme gen-hostnqn > ${sysconfdir}/nvme/hostnqn 20 ${bindir}/uuidgen > ${sysconfdir}/nvme/hostid 34 # git/plugins/virtium/virtium-nvme.c:205:63: error: passing argument 1 of 'localtime' from incompat…
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
H A D | KeyPolicy.v1_0_1.json | 109 "description": "NVMe-oF specific properties.", 110 …"longDescription": "This property shall contain NVMe-oF specific properties for this key policy. … 138 "NVMeoF": "An NVMe-oF key policy." 141 "NVMeoF": "This value shall indicate the key policy is for an NVMe-oF key." 147 "description": "NVMe-oF specific properties.", 148 … "longDescription": "This type shall contain NVMe-oF specific properties for a key policy.", 204 … contain the OEM-defined security protocols that this key policy allows. NVMe-oF channels are res… 236 …operty shall contain the security protocols that this key policy allows. NVMe-oF channels are res… 260 "description": "The NVMe cipher suites that a key is allowed to use.", 270 …as defined by the 'Mandatory and Recommended Cipher Suites' clause in the NVMe TCP Transport Speci… [all …]
|
H A D | StorageControllerMetrics.v1_0_3.json | 37 …"longDescription": "The object shall contain the NVMe-defined 'Endurance Group Critical Warning Su… 85 "description": "The NVMe SMART metrics.", 86 …"longDescription": "This object shall contain the NVMe SMART metrics as defined by the NVMe SMART/… 104 …"longDescription": "This property shall contain the NVMe-defined 'Available Spare', which represen… 116 …"longDescription": "This property shall contain the NVMe-defined 'Available Spare Threshold' as a … 128 …s for this storage controller. Services shall derive this value from the NVMe-defined 'Composite … 138 …"longDescription": "This property shall contain the NVMe-defined 'Controller Busy Time', which rep… 147 …"longDescription": "This property shall contain the NVMe-defined 'Critical Composite Temperature T… 156 "description": "The NVMe SMART critical warnings.", 157 … "longDescription": "The property shall contain the NVMe-defined 'Critical Warning'." [all …]
|
H A D | Key.v1_4_1.json | 109 "description": "NVMe-oF specific properties.", 110 …"longDescription": "This property shall contain NVMe-oF specific properties for this key. This pr… 156 "NVMeoF": "An NVMe-oF key.", 160 …": "This value shall indicate the format of the key is defined by one of the NVMe specifications.", 170 "description": "NVMe-oF specific properties.", 171 "longDescription": "This type shall contain NVMe-oF specific properties for a key.", 197 …"description": "The NVMe Qualified Name (NQN) of the host or target subsystem associated with this… 198 …NVMe Qualified Name (NQN) of the host or target subsystem associated with this key. The value of … 250 "description": "The NVMe secure hash algorithms that a key is allowed to use.", 262 … as defined by the 'DH-HMAC-CHAP hash function identifiers' figure in the NVMe Base Specification.… [all …]
|
/openbmc/u-boot/include/ |
H A D | nvme.h | 15 * This issues an identify command to the NVMe controller to return a data 18 * @dev: NVMe controller device 33 * @dev: NVMe controller device 49 * @dev: NVMe controller device 61 * nvme_scan_namespace - scan all namespaces attached to NVMe controllers 63 * This probes all registered NVMe uclass device drivers in the system, 64 * and tries to find all namespaces attached to the NVMe controllers. 71 * nvme_print_info - print detailed NVMe controller and namespace information 73 * This prints out detailed human readable NVMe controller and namespace 76 * @udev: NVMe controller device [all …]
|
/openbmc/entity-manager/configurations/meta/clemente/ |
H A D | clemente_hdd_nvme.json | 7 "Name": "NVMe $index FRU", 46 /* Clemente Hard Disk Drive NVMe Board 0*/ 47 "Name": "Clemente HDD NVMe 0 $bus - 48 / 2", 55 "Type": "NVMe", 69 "Name": "NVMe $index FRU", 108 /* Clemente Hard Disk Drive NVMe Board 1*/ 109 "Name": "Clemente HDD NVMe 1 $bus - 52 / 2", 117 "Type": "NVMe", 131 "Name": "NVMe $index FRU", 156 /* Clemente Boot Drive NVMe*/ [all …]
|
/openbmc/entity-manager/configurations/ampere/ |
H A D | mtjefferson_bp.json | 18 "Name": "nvme$ADDRESS / 82 * 8 + 0", 24 "Name": "nvme$ADDRESS / 82 * 8 + 1", 30 "Name": "nvme$ADDRESS / 82 * 8 + 2", 36 "Name": "nvme$ADDRESS / 82 * 8 + 3", 42 "Name": "nvme$ADDRESS / 82 * 8 + 4", 48 "Name": "nvme$ADDRESS / 82 * 8 + 5", 54 "Name": "nvme$ADDRESS / 82 * 8 + 6", 60 "Name": "nvme$ADDRESS / 82 * 8 + 7",
|
H A D | mtmitchell_bp.json | 12 "Name": "nvme$BUS % 100 * 8 + 0", 18 "Name": "nvme$BUS % 100 * 8 + 1", 24 "Name": "nvme$BUS % 100 * 8 + 2", 30 "Name": "nvme$BUS % 100 * 8 + 3", 36 "Name": "nvme$BUS % 100 * 8 + 4", 42 "Name": "nvme$BUS % 100 * 8 + 5", 48 "Name": "nvme$BUS % 100 * 8 + 6", 54 "Name": "nvme$BUS % 100 * 8 + 7",
|
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
H A D | KeyPolicy_v1.xml | 77 <Annotation Term="OData.Description" String="NVMe-oF specific properties."/> 78 …<Annotation Term="OData.LongDescription" String="This property shall contain NVMe-oF specific prop… 88 <Annotation Term="OData.Description" String="An NVMe-oF key policy."/> 89 …="OData.LongDescription" String="This value shall indicate the key policy is for an NVMe-oF key."/> 95 <Annotation Term="OData.Description" String="NVMe-oF specific properties."/> 96 …<Annotation Term="OData.LongDescription" String="This type shall contain NVMe-oF specific properti… 100 …operty shall contain the security protocols that this key policy allows. NVMe-oF channels are res… 105 … contain the OEM-defined security protocols that this key policy allows. NVMe-oF channels are res… 130 …<Annotation Term="OData.Description" String="The NVMe security protocols that a key is allowed to … 131 …<Annotation Term="OData.LongDescription" String="This enumeration shall list the NVMe security pro… [all …]
|
/openbmc/openbmc/meta-quanta/meta-gbs/recipes-phosphor/sensors/phosphor-nvme/ |
H A D | xyz.openbmc_project.nvme.manager.service.replace | 2 Description=NVMe management 5 Wants=mapper-wait@-xyz-openbmc_project-control-nvme.service 6 After=mapper-wait@-xyz-openbmc_project-control-nvme.service 12 BusName=xyz.openbmc_project.nvme.manager 13 SyslogIdentifier=phosphor-nvme
|
/openbmc/openbmc/meta-phosphor/recipes-phosphor/sensors/ |
H A D | phosphor-nvme_git.bb | 1 SUMMARY = "NVMe Drive Manager" 2 DESCRIPTION = "Daemon to monitor and report the status of NVMe drives" 3 HOMEPAGE = "https://github.com/openbmc/phosphor-nvme" 15 SRC_URI = "git://github.com/openbmc/phosphor-nvme.git;protocol=https;branch=master" 18 SYSTEMD_SERVICE:${PN} = "xyz.openbmc_project.nvme.manager.service"
|
/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/Nvme/ |
H A D | meson.build | 4 sdbusplus_current_path = 'xyz/openbmc_project/Nvme' 7 'xyz/openbmc_project/Nvme/Status__markdown'.underscorify(), 9 '../../../../yaml/xyz/openbmc_project/Nvme/Status.errors.yaml', 10 '../../../../yaml/xyz/openbmc_project/Nvme/Status.interface.yaml', 24 'xyz/openbmc_project/Nvme/Status',
|
/openbmc/openbmc/meta-quanta/meta-gbs/recipes-phosphor/sensors/ |
H A D | phosphor-nvme_%.bbappend | 4 SRC_URI:append:gbs = " file://xyz.openbmc_project.nvme.manager.service.replace" 9 install -d ${D}/${sysconfdir}/nvme/ 10 install -m 0644 ${UNPACKDIR}/nvme_config.json ${D}/${sysconfdir}/nvme/ 16 …4 ${UNPACKDIR}/xyz.openbmc_project.nvme.manager.service.replace ${D}${systemd_system_unitdir}/xyz.…
|
/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/Nvme/Status/ |
H A D | meson.build | 3 sdbusplus_current_path = 'xyz/openbmc_project/Nvme/Status' 6 'xyz/openbmc_project/Nvme/Status__cpp'.underscorify(), 8 '../../../../../yaml/xyz/openbmc_project/Nvme/Status.errors.yaml', 9 '../../../../../yaml/xyz/openbmc_project/Nvme/Status.interface.yaml', 31 'xyz/openbmc_project/Nvme/Status',
|
/openbmc/phosphor-fan-presence/control/config_files/p10bmc/com.ibm.Hardware.Chassis.Model.Rainier2U/ |
H A D | pcie_cards.json | 68 "name": "Bolt PCIe3 NVMe Flash Adapter II x8 1.6TB", 76 "name": "Bolt PCIe3 NVMe Flash Adapter II x8 3.2TB", 84 "name": "Bolt PCIe3 NVMe Flash Adapter II x8 6.4TB", 92 "name": "Bolt PCIe3 NVMe Flash Adapter III x8 1.6TB", 100 "name": "Bolt PCIe3 NVMe Flash Adapter III x8 3.2TB", 108 "name": "Bolt PCIe3 NVMe Flash Adapter III x8 6.4TB", 116 "name": "Kona PCIe4 NVMe U.2 Flash Adapter x8 1.6TB", 124 "name": "Kona PCIe4 NVMe U.2 Flash Adapter x8 3.2TB", 132 "name": "Kona PCIe4 NVMe U.2 Flash Adapter x8 6.4TB",
|
/openbmc/entity-manager/configurations/ |
H A D | micron_7450.json |
|
/openbmc/phosphor-fan-presence/control/config_files/p10bmc/com.ibm.Hardware.Chassis.Model.Rainier1S4U/ |
H A D | pcie_cards.json | 52 "name": "Bolt PCIe3 NVMe Flash Adapter II x8 1.6TB", 60 "name": "Bolt PCIe3 NVMe Flash Adapter II x8 3.2TB", 68 "name": "Bolt PCIe3 NVMe Flash Adapter II x8 6.4TB", 76 "name": "Bolt PCIe3 NVMe Flash Adapter III x8 1.6TB", 84 "name": "Bolt PCIe3 NVMe Flash Adapter III x8 3.2TB", 92 "name": "Bolt PCIe3 NVMe Flash Adapter III x8 6.4TB", 148 "name": "Kona PCIe4 NVMe U.2 Flash Adapter x8 1.6TB", 156 "name": "Kona PCIe4 NVMe U.2 Flash Adapter x8 3.2TB", 164 "name": "Kona PCIe4 NVMe U.2 Flash Adapter x8 6.4TB",
|
/openbmc/phosphor-fan-presence/control/config_files/p10bmc/com.ibm.Hardware.Chassis.Model.BlueRidge2U/ |
H A D | pcie_cards.json | 68 "name": "Bolt PCIe3 NVMe Flash Adapter II x8 1.6TB", 76 "name": "Bolt PCIe3 NVMe Flash Adapter II x8 3.2TB", 84 "name": "Bolt PCIe3 NVMe Flash Adapter II x8 6.4TB", 92 "name": "Bolt PCIe3 NVMe Flash Adapter III x8 1.6TB", 100 "name": "Bolt PCIe3 NVMe Flash Adapter III x8 3.2TB", 108 "name": "Bolt PCIe3 NVMe Flash Adapter III x8 6.4TB", 116 "name": "Kona PCIe4 NVMe U.2 Flash Adapter x8 1.6TB", 124 "name": "Kona PCIe4 NVMe U.2 Flash Adapter x8 3.2TB", 132 "name": "Kona PCIe4 NVMe U.2 Flash Adapter x8 6.4TB",
|
/openbmc/phosphor-fan-presence/control/config_files/p10bmc/com.ibm.Hardware.Chassis.Model.Rainier4U/ |
H A D | pcie_cards.json | 68 "name": "Bolt PCIe3 NVMe Flash Adapter II x8 1.6TB", 76 "name": "Bolt PCIe3 NVMe Flash Adapter II x8 3.2TB", 84 "name": "Bolt PCIe3 NVMe Flash Adapter II x8 6.4TB", 92 "name": "Bolt PCIe3 NVMe Flash Adapter III x8 1.6TB", 100 "name": "Bolt PCIe3 NVMe Flash Adapter III x8 3.2TB", 108 "name": "Bolt PCIe3 NVMe Flash Adapter III x8 6.4TB", 164 "name": "Kona PCIe4 NVMe U.2 Flash Adapter x8 1.6TB", 172 "name": "Kona PCIe4 NVMe U.2 Flash Adapter x8 3.2TB", 180 "name": "Kona PCIe4 NVMe U.2 Flash Adapter x8 6.4TB",
|