diff options
| author | Simon Glass <[email protected]> | 2023-01-17 10:48:19 -0700 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2023-01-23 18:11:41 -0500 |
| commit | 1bdda5fd727dbce58d09846956ae8a21621b4082 (patch) | |
| tree | c3c7796122d5ccbcaf1105fd62e6f96e2cd44fef /doc/develop/driver-model | |
| parent | f738c73a2b0e03840fe5a9540aa84115f20b41e2 (diff) | |
bootstd: Update documentation for new features
Document the hunters and the new way that iteration works.
Signed-off-by: Simon Glass <[email protected]>
Diffstat (limited to 'doc/develop/driver-model')
| -rw-r--r-- | doc/develop/driver-model/nvme.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/develop/driver-model/nvme.rst b/doc/develop/driver-model/nvme.rst index fd0c0f00d2d..75518133121 100644 --- a/doc/develop/driver-model/nvme.rst +++ b/doc/develop/driver-model/nvme.rst @@ -27,7 +27,7 @@ How it works ------------ There is an NVMe uclass driver (driver name "nvme"), an NVMe host controller driver (driver name "nvme") and an NVMe namespace block driver (driver name -"nvme-blk"). The host controller driver is supposed to probe the hardware and +"nvme_blk"). The host controller driver is supposed to probe the hardware and do necessary initialization to put the controller into a ready state at which it is able to scan all available namespaces attached to it. Scanning namespace is triggered by the NVMe uclass driver and the actual work is done in the NVMe |