diff options
author | Moshe Shemesh <moshe@mellanox.com> | 2020-10-07 09:00:43 +0300 |
---|---|---|
committer | Jakub Kicinski <kuba@kernel.org> | 2020-10-09 22:06:52 +0300 |
commit | ccdf07219da6bd1f43c6ddcde4c0e36993c7365a (patch) | |
tree | e25b00e0e3e2d473aceea640aa9ead07b91a6f08 /include/keys | |
parent | 69d56e0ea0ee9c61fa70c144449945ebaedb9dfa (diff) | |
download | linux-ccdf07219da6bd1f43c6ddcde4c0e36993c7365a.tar.xz |
devlink: Add reload action option to devlink reload command
Add devlink reload action to allow the user to request a specific reload
action. The action parameter is optional, if not specified then devlink
driver re-init action is used (backward compatible).
Note that when required to do firmware activation some drivers may need
to reload the driver. On the other hand some drivers may need to reset
the firmware to reinitialize the driver entities. Therefore, the devlink
reload command returns the actions which were actually performed.
Reload actions supported are:
driver_reinit: driver entities re-initialization, applying devlink-param
and devlink-resource values.
fw_activate: firmware activate.
command examples:
$devlink dev reload pci/0000:82:00.0 action driver_reinit
reload_actions_performed:
driver_reinit
$devlink dev reload pci/0000:82:00.0 action fw_activate
reload_actions_performed:
driver_reinit fw_activate
Signed-off-by: Moshe Shemesh <moshe@mellanox.com>
Reviewed-by: Jakub Kicinski <kuba@kernel.org>
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/keys')
0 files changed, 0 insertions, 0 deletions