summaryrefslogtreecommitdiff
path: root/drivers/ufs
diff options
context:
space:
mode:
authorPeter Wang <peter.wang@mediatek.com>2026-02-10 14:41:44 +0800
committerMartin K. Petersen <martin.petersen@oracle.com>2026-02-24 13:40:01 -0500
commit3abe4113e784b4a1135fe0e89828afecbfebf862 (patch)
tree57052fd30ea67b83d540c028c5aae98f90ff6421 /drivers/ufs
parent01517654bc258efb2610e53e99fa4ef641d134b9 (diff)
downloadlwn-3abe4113e784b4a1135fe0e89828afecbfebf862.tar.gz
lwn-3abe4113e784b4a1135fe0e89828afecbfebf862.zip
scsi: ufs: core: Add debug log for MCQ command timeout
It is difficult to debug situations where an MCQ command timeout occurs, the corresponding CQ tag response is received, but the request is not completed. Add a one-line log to indicate when the CQ entry is abnormal. Signed-off-by: Peter Wang <peter.wang@mediatek.com> Reviewed-by: Bart Van Assche <bvanassche@acm.org> Link: https://patch.msgid.link/20260210070837.1820710-3-peter.wang@mediatek.com Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'drivers/ufs')
-rw-r--r--drivers/ufs/core/ufs-mcq.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/ufs/core/ufs-mcq.c b/drivers/ufs/core/ufs-mcq.c
index 18a95b728633..eb3770830d73 100644
--- a/drivers/ufs/core/ufs-mcq.c
+++ b/drivers/ufs/core/ufs-mcq.c
@@ -301,6 +301,8 @@ static void ufshcd_mcq_process_cqe(struct ufs_hba *hba,
ufshcd_compl_one_cqe(hba, tag, cqe);
/* After processed the cqe, mark it empty (invalid) entry */
cqe->command_desc_base_addr = 0;
+ } else {
+ dev_err(hba->dev, "Abnormal CQ entry!\n");
}
}