提交 e240537b 编写于 作者: V Vladimir Kondratiev 提交者: John W. Linville

wil6210: improve dmesg for fw error handling

In case of FW error, make it clear (in dmesg) what branch is taken
in the error recovery code.
Signed-off-by: NVladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
上级 b516fcc5
...@@ -267,9 +267,12 @@ static void wil_fw_error_worker(struct work_struct *work) ...@@ -267,9 +267,12 @@ static void wil_fw_error_worker(struct work_struct *work)
break; break;
case NL80211_IFTYPE_AP: case NL80211_IFTYPE_AP:
case NL80211_IFTYPE_P2P_GO: case NL80211_IFTYPE_P2P_GO:
wil_info(wil, "No recovery for AP-like interface\n");
/* recovery in these modes is done by upper layers */ /* recovery in these modes is done by upper layers */
break; break;
default: default:
wil_err(wil, "No recovery - unknown interface type %d\n",
wdev->iftype);
break; break;
} }
mutex_unlock(&wil->mutex); mutex_unlock(&wil->mutex);
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册