Commit 15d74e65 authored by Jiri Pirko's avatar Jiri Pirko Committed by Paolo Abeni

Documentation: devlink: extend reload-reinit description

Be more explicit about devlink entities that may stay and that have to
be removed during reload reinit action.
Signed-off-by: default avatarJiri Pirko <jiri@nvidia.com>
Reviewed-by: default avatarPrzemek Kitszel <przemyslaw.kitszel@intel.com>
Signed-off-by: default avatarPaolo Abeni <pabeni@redhat.com>
parent e3517426
...@@ -22,8 +22,17 @@ By default ``driver_reinit`` action is selected. ...@@ -22,8 +22,17 @@ By default ``driver_reinit`` action is selected.
* - ``driver-reinit`` * - ``driver-reinit``
- Devlink driver entities re-initialization, including applying - Devlink driver entities re-initialization, including applying
new values to devlink entities which are used during driver new values to devlink entities which are used during driver
load such as ``devlink-params`` in configuration mode load which are:
``driverinit`` or ``devlink-resources``
* ``devlink-params`` in configuration mode ``driverinit``
* ``devlink-resources``
Other devlink entities may stay over the re-initialization:
* ``devlink-health-reporter``
* ``devlink-region``
The rest of the devlink entities have to be removed and readded.
* - ``fw_activate`` * - ``fw_activate``
- Firmware activate. Activates new firmware if such image is stored and - Firmware activate. Activates new firmware if such image is stored and
pending activation. If no limitation specified this action may involve pending activation. If no limitation specified this action may involve
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment