From 02e2e69508469b78b6da4fe5a2ec3598cc66afdb Mon Sep 17 00:00:00 2001 From: Sreelakshmi Konamki Date: Thu, 11 Aug 2016 14:23:40 +0530 Subject: qcacld-2.0: Flush driver and firmware logs only for driver ring id Currently driver flushes driver and firmware logs irrespective of ring id. Host should flush the logs only for driver ring id. Add changes to fix the same issue. Change-Id: I50cfde1baaf18c1a3992f956182b49044ccc4b1d CRs-Fixed: 1053219 --- CORE/HDD/src/wlan_hdd_cfg80211.c | 25 +++++++++++++++---------- 1 file changed, 15 insertions(+), 10 deletions(-) diff --git a/CORE/HDD/src/wlan_hdd_cfg80211.c b/CORE/HDD/src/wlan_hdd_cfg80211.c index e8e29397f793..bb54a6536802 100644 --- a/CORE/HDD/src/wlan_hdd_cfg80211.c +++ b/CORE/HDD/src/wlan_hdd_cfg80211.c @@ -9274,17 +9274,22 @@ static int __wlan_hdd_cfg80211_wifi_logger_get_ring_data(struct wiphy *wiphy, hddLog(LOG1, FL("Flushing/Retrieving packet stats")); } - hddLog(LOG1, FL("Bug report triggered by framework")); - - ret = vos_flush_logs(WLAN_LOG_TYPE_NON_FATAL, - WLAN_LOG_INDICATOR_FRAMEWORK, - WLAN_LOG_REASON_CODE_UNUSED, - true); - if (VOS_STATUS_SUCCESS != ret) { - hddLog(LOGE, FL("Failed to trigger bug report")); - return -EINVAL; + /* + * As part of DRIVER ring ID, flush both driver and firmware logs. + * For other Ring ID's driver doesn't have any rings to flush + */ + if (ring_id == RING_ID_DRIVER_DEBUG) { + hddLog(LOG1, FL("Bug report triggered by framework")); + + ret = vos_flush_logs(WLAN_LOG_TYPE_NON_FATAL, + WLAN_LOG_INDICATOR_FRAMEWORK, + WLAN_LOG_REASON_CODE_UNUSED, + true); + if (VOS_STATUS_SUCCESS != ret) { + hddLog(LOGE, FL("Failed to trigger bug report")); + return -EINVAL; + } } - return 0; } -- cgit v1.2.3