From: "DooHyun Hwang" <dh0421.hwang@samsung.com>
To: "'Avri Altman'" <Avri.Altman@sandisk.com>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<alim.akhtar@samsung.com>, <avri.altman@wdc.com>,
<bvanassche@acm.org>, <James.Bottomley@HansenPartnership.com>,
<martin.petersen@oracle.com>, <peter.wang@mediatek.com>,
<manivannan.sadhasivam@linaro.org>, <quic_mnaresh@quicinc.com>
Cc: <grant.jung@samsung.com>, <jt77.jang@samsung.com>,
<junwoo80.lee@samsung.com>, <jangsub.yi@samsung.com>,
<sh043.lee@samsung.com>, <cw9316.lee@samsung.com>,
<sh8267.baek@samsung.com>, <wkon.kim@samsung.com>
Subject: RE: [PATCH 1/2] scsi: ufs: Add an enum for ufs_trace to check ufs cmd error
Date: Thu, 17 Apr 2025 17:21:39 +0900 [thread overview]
Message-ID: <055d01dbaf71$be2da7f0$3a88f7d0$@samsung.com> (raw)
In-Reply-To: <PH7PR16MB6196EF7F7A1862B48B66C5C5E5BC2@PH7PR16MB6196.namprd16.prod.outlook.com>
> > There is no trace when a ufs uic cmd error occurs.
> > So, add "UFS_CMD_ERR" enumeration to ufs_trace_str_t.
> >
> > Signed-off-by: DooHyun Hwang <dh0421.hwang@samsung.com>
> > ---
> > drivers/ufs/core/ufs_trace.h | 1 +
> > include/ufs/ufs.h | 2 +-
> > 2 files changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/ufs/core/ufs_trace.h b/drivers/ufs/core/ufs_trace.h
> index
> > caa32e23ffa5..43830a092637 100644
> > --- a/drivers/ufs/core/ufs_trace.h
> > +++ b/drivers/ufs/core/ufs_trace.h
> > @@ -41,6 +41,7 @@
> > #define UFS_CMD_TRACE_STRINGS \
> > EM(UFS_CMD_SEND, "send_req") \
> > EM(UFS_CMD_COMP, "complete_rsp") \
> > + EM(UFS_CMD_ERR, "req_complete_err") \
> > EM(UFS_DEV_COMP, "dev_complete") \
> > EM(UFS_QUERY_SEND, "query_send") \
> > EM(UFS_QUERY_COMP, "query_complete") \
> > diff --git a/include/ufs/ufs.h b/include/ufs/ufs.h index
> > c0c59a8f7256..7f2d418bdd86 100644
> > --- a/include/ufs/ufs.h
> > +++ b/include/ufs/ufs.h
> > @@ -631,7 +631,7 @@ struct ufs_dev_info {
> > * This enum is used in string mapping in ufs_trace.h.
> > */
> > enum ufs_trace_str_t {
> > - UFS_CMD_SEND, UFS_CMD_COMP, UFS_DEV_COMP,
> > + UFS_CMD_SEND, UFS_CMD_COMP, UFS_CMD_ERR, UFS_DEV_COMP,
> > UFS_QUERY_SEND, UFS_QUERY_COMP, UFS_QUERY_ERR,
> > UFS_TM_SEND, UFS_TM_COMP, UFS_TM_ERR };
> It seems strange to me that scsi & uic commands are designated by the same
> enum.
> Has it been considered to add UFS_UIC_SEND, UFS_UIC_COMP, UFS_UIC_ERR to
> enum ufs_trace_str_t ?
> Also looks like UFS_DEV_COMP is unused ?
>
> Thanks,
> Avri
It is correct that the same enumeration is used for both SCSI and UIC
commands.
However, the trace function differs for SCSI and UIC commands.
The enum is solely for handling the sending and completion of each command
within the respective trace functions.
Therefore, I think there is no need to add new enums like "UFS_UIC_SEND".
It seems better to discuss "UFS_DEV_COMP" in another commit.
Thank you.
DooHyun Hwang.
> > --
> > 2.48.1
>
next prev parent reply other threads:[~2025-04-17 8:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250417023415epcas1p47da6d269afcb5d1807004c9b708675a5@epcas1p4.samsung.com>
2025-04-17 2:34 ` [PATCH 0/2] scsi: ufs: Add an enum for ufs_trace_str_t to check uic cmd error DooHyun Hwang
2025-04-17 2:34 ` [PATCH 1/2] scsi: ufs: Add an enum for ufs_trace to check ufs " DooHyun Hwang
2025-04-17 4:59 ` Avri Altman
2025-04-17 8:21 ` DooHyun Hwang [this message]
2025-08-29 15:15 ` Bart Van Assche
2025-09-01 1:31 ` DooHyun Hwang
2025-09-01 14:03 ` Bart Van Assche
2025-09-02 1:09 ` DooHyun Hwang
2025-09-02 16:34 ` Bart Van Assche
2025-09-03 6:39 ` DooHyun Hwang
2025-09-03 15:56 ` Bart Van Assche
2025-09-08 7:43 ` DooHyun Hwang
2025-09-08 15:27 ` Bart Van Assche
2025-04-17 2:34 ` [PATCH 2/2] scsi: ufs: core: Add a trace function calling when uic command error occurs DooHyun Hwang
2025-04-17 21:35 ` Bart Van Assche
2025-04-18 4:48 ` DooHyun Hwang
2025-04-22 12:48 ` Peter Wang (王信友)
2025-04-23 6:45 ` DooHyun Hwang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='055d01dbaf71$be2da7f0$3a88f7d0$@samsung.com' \
--to=dh0421.hwang@samsung.com \
--cc=Avri.Altman@sandisk.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=cw9316.lee@samsung.com \
--cc=grant.jung@samsung.com \
--cc=jangsub.yi@samsung.com \
--cc=jt77.jang@samsung.com \
--cc=junwoo80.lee@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=martin.petersen@oracle.com \
--cc=peter.wang@mediatek.com \
--cc=quic_mnaresh@quicinc.com \
--cc=sh043.lee@samsung.com \
--cc=sh8267.baek@samsung.com \
--cc=wkon.kim@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox