diff options
| author |   Oded Gabbay <ogabbay@kernel.org> | 2022-04-02 22:09:16 +0300 |
|---|---|---|
| committer |   Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-05-22 21:01:17 +0200 |
| commit | c82b025f2b8cf3c1e0f6dcca52ece71fba4f8b12 (patch) | |
| tree | 71a5a197e050ec87ffca4269b4e587a730395e89 /drivers/misc | |
| parent | habanalabs: change a reset print to debug level (diff) | |
| download | linux-dev-c82b025f2b8cf3c1e0f6dcca52ece71fba4f8b12.tar.xz linux-dev-c82b025f2b8cf3c1e0f6dcca52ece71fba4f8b12.zip | |
habanalabs: don't print normal reset operations
Only a hard-reset is an unexpected event which should be notify in
the kernel log. Other resets are normal operations and therefore
we should not pollute the log with them.
Signed-off-by: Oded Gabbay <ogabbay@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/misc')
| -rw-r--r-- | drivers/misc/habanalabs/common/device.c | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/drivers/misc/habanalabs/common/device.c b/drivers/misc/habanalabs/common/device.c index 9a71737fc804..48654dfcd7b6 100644 --- a/drivers/misc/habanalabs/common/device.c +++ b/drivers/misc/habanalabs/common/device.c @@ -1198,9 +1198,9 @@ do_reset: if (hard_reset) dev_info(hdev->dev, "Going to reset device\n"); else if (reset_upon_device_release) - dev_info(hdev->dev, "Going to reset device after release by user\n"); + dev_dbg(hdev->dev, "Going to reset device after release by user\n"); else - dev_info(hdev->dev, "Going to reset engines of inference device\n"); + dev_dbg(hdev->dev, "Going to reset engines of inference device\n"); } again: @@ -1406,7 +1406,10 @@ kill_processes: hdev->reset_info.needs_reset = false; - dev_notice(hdev->dev, "Successfully finished resetting the device\n"); + if (hard_reset) + dev_info(hdev->dev, "Successfully finished resetting the device\n"); + else + dev_dbg(hdev->dev, "Successfully finished resetting the device\n"); if (hard_reset) { hdev->reset_info.hard_reset_cnt++; |