From 0fdc03e41ed2d9d0e9fbdb4bf8da589f27fd0cb1 Mon Sep 17 00:00:00 2001 From: Alan Chen Date: Tue, 15 Oct 2019 14:56:07 -0700 Subject: [PATCH] qcacmn: Log timer callback info If qdf timer is already running and a module calls it again, log the timer callback info to see why that module is calling it again. Change-Id: I47e9d33a2a144a0a779f71b50dbabea227c4b362 CRs-Fixed: 2546070 --- qdf/linux/src/qdf_mc_timer.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/qdf/linux/src/qdf_mc_timer.c b/qdf/linux/src/qdf_mc_timer.c index 451986a60c96..a26601b60dea 100644 --- a/qdf/linux/src/qdf_mc_timer.c +++ b/qdf/linux/src/qdf_mc_timer.c @@ -670,8 +670,8 @@ QDF_STATUS qdf_mc_timer_start(qdf_mc_timer_t *timer, uint32_t expiration_time) if (QDF_TIMER_STATE_STOPPED != timer->state) { qdf_spin_unlock_irqrestore(&timer->platform_info.spinlock); QDF_TRACE(QDF_MODULE_ID_QDF, QDF_TRACE_LEVEL_ERROR, - "%s: Cannot start timer in state = %d ", __func__, - timer->state); + "%s: Cannot start timer in state = %d %ps", + __func__, timer->state, (void *)timer->callback); return QDF_STATUS_E_ALREADY; }