From: "Powen Kao (高伯文)" <Powen.Kao@mediatek.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"quic_nguyenb@quicinc.com" <quic_nguyenb@quicinc.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"quic_ziqichen@quicinc.com" <quic_ziqichen@quicinc.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>
Cc: "Peter Wang (王信友)" <peter.wang@mediatek.com>,
"Eddie Huang (黃智傑)" <eddie.huang@mediatek.com>,
"Jiajie Hao (郝加节)" <jiajie.hao@mediatek.com>,
"CC Chou (周志杰)" <cc.chou@mediatek.com>,
"Alice Chao (趙珮均)" <Alice.Chao@mediatek.com>,
wsd_upstream <wsd_upstream@mediatek.com>,
"Chun-Hung Wu (巫駿宏)" <Chun-hung.Wu@mediatek.com>,
"quic_asutoshd@quicinc.com" <quic_asutoshd@quicinc.com>,
"Chaotian Jing (井朝天)" <Chaotian.Jing@mediatek.com>,
"Naomi Chu (朱詠田)" <Naomi.Chu@mediatek.com>,
"Stanley Chu (朱原陞)" <stanley.chu@mediatek.com>,
"Mason Zhang (章辉)" <Mason.Zhang@mediatek.com>,
"quic_cang@quicinc.com" <quic_cang@quicinc.com>
Subject: Re: [PATCH v2 4/7] scsi: ufs: core: Add hwq print for debug
Date: Wed, 1 Mar 2023 02:17:32 +0000 [thread overview]
Message-ID: <f629f1b72e4859d79aac279ef3327715000e3210.camel@mediatek.com> (raw)
In-Reply-To: <76f74b86-8ff1-2346-4f5e-0048543bd8b0@quicinc.com>
Hi Bao,
Sure, we can first integrate ur patch and see if anything is missing
that need further upstream. Due to comapct schedule, I would kindly ask
if it will be ready by the end of this week? :) Thanks
On Mon, 2023-02-27 at 18:57 -0800, Bao D. Nguyen wrote:
> On 2/26/2023 7:14 Sure PM, Ziqi Chen wrote:
> > Hi Powen,
> >
> > The Bao. D . Nguyen (quic_nguyenb@quicinc.com) from QCOM already
> > made
> > patch to support MCQ abort.
> >
> > ++ Bao here to be aware of it in case your error handing patch
> > conflict with his abort handling patch.
> >
> >
> > Best Regards,
> >
> > Ziqi
> >
> >
> > On 2/23/2023 10:13 PM, Powen Kao (高伯文) wrote:
> > > Hi Ziqi,
> > >
> > > Thanks for ur comments.
> > >
> > > This piece of code successfully dump relevent registers on our
> > > platform. As you know, mcq error handling flow is not ready yet
> > > so the
> > > insertion point might not seems to be reasonable.
> > >
> > > Maybe drop this patch for now, I will send it later with error
> > > handling
> > > patches.
> > >
> > >
> > > On Thu, 2023-02-23 at 18:14 +0800, Ziqi Chen wrote:
> > > > Hi Po-Wen,
> > > >
> > > > On 2/22/2023 11:04 AM, Po-Wen Kao wrote:
> > > > > +void ufshcd_mcq_print_hwqs(struct ufs_hba *hba, unsigned
> > > > > long
> > > > > bitmap)
> > > > > +{
> > > > > + int id, i;
> > > > > + char prefix[15];
> > > > > +
> > > > > + if (!is_mcq_enabled(hba))
> > > > > + return;
> > > > > +
> > > > > + for_each_set_bit(id, &bitmap, hba->nr_hw_queues) {
> > > > > + snprintf(prefix, sizeof(prefix), "q%d SQCFG: ", id);
> > > > > + ufshcd_hex_dump(prefix,
> > > > > + hba->mcq_base + MCQ_QCFG_SIZE * id,
> > > > > MCQ_QCFG_SQ_SIZE);
> > > >
> > > > Is your purpose dump per hardware queue registers here? If
> > > > yes, why
> > > > don't use ufsmcq_readl() to save to a buffer and then use
> > > > ufshcd_hex_dump()
> > > >
> > > > to dump ? Are you sure ufshcd_hex_dump() can dump register
> > > > directly?
> > > >
> > > > > +
> > > > > + snprintf(prefix, sizeof(prefix), "q%d CQCFG: ", id);
> > > > > + ufshcd_hex_dump(prefix,
> > > > > + hba->mcq_base + MCQ_QCFG_SIZE * id +
> > > > > MCQ_QCFG_SQ_SIZE, MCQ_QCFG_CQ_SIZE);
> > > >
> > > > Same to above comment.
> > > > > +
> > > > > + for (i = 0; i < OPR_MAX ; i++) {
> > > > > + snprintf(prefix, sizeof(prefix), "q%d OPR%d: ",
> > > > > id, i);
> > > > > + ufshcd_hex_dump(prefix, mcq_opr_base(hba, i,
> > > > > id), mcq_opr_size[i]);
> > > >
> > > > Same.
> > > > > + }
> > > > > + }
> > > > > +}
> > > > > +
> > > > >
> > > > > @@ -574,7 +569,16 @@ void ufshcd_print_trs(struct ufs_hba
> > > > > *hba,
> > > > > unsigned long bitmap, bool pr_prdt)
> > > > > if (pr_prdt)
> > > > > ufshcd_hex_dump("UPIU PRDT: ", lrbp-
> > > > > > ucd_prdt_ptr,
> > > > >
> > > > > ufshcd_sg_entry_size(hba) *
> > > > > prdt_length);
> > > > > +
> > > > > + if (is_mcq_enabled(hba)) {
> > > > > + cmd = lrbp->cmd;
> > > > > + if (!cmd)
> > > > > + return;
> > > > > + hwq = ufshcd_mcq_req_to_hwq(hba,
> > > > > scsi_cmd_to_rq(cmd));
> > > > > + ufshcd_mcq_print_hwqs(hba, 1 << hwq->id);
> > > >
> > > > Calling registers dump function in ufshcd_print_trs() is not
> > > > reasonable,
> > > > eg.. for each aborted request, it would print out all hwq
> > > > registers,
> > > > it's not make sense.
> > > >
> > > > I think we should move it out of ufshcd_print_trs().
> > > >
> > > > > + }
> > > > > }
> > > > > +
> > > > > }
> > > >
> > > > Best Regards,
> > > >
> > > > Ziqi
> > > >
>
> Hi Powen,
>
> I am going to push the mcq abort handling and mcq error handling
> code
> upstream for review in a couple days. Would that work for you?
>
> Regards,
> Bao
>
next prev parent reply other threads:[~2023-03-01 2:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 3:04 [PATCH v2 0/7] Several UFS MCQ Code Changes Po-Wen Kao
2023-02-22 3:04 ` [PATCH v2 1/7] scsi: ufs: core: Fix mcq tag calcualtion Po-Wen Kao
2023-02-23 10:22 ` Ziqi Chen
2023-02-22 3:04 ` [PATCH v2 2/7] scsi: ufs: core: Rename symbols Po-Wen Kao
2023-02-22 3:11 ` Stanley Chu
2023-02-23 10:27 ` Ziqi Chen
2023-02-27 22:41 ` Bart Van Assche
2023-02-22 3:04 ` [PATCH v2 3/7] scsi: ufs: core: Fix mcq nr_hw_queues Po-Wen Kao
2023-02-22 3:16 ` Stanley Chu
2023-02-23 10:32 ` Ziqi Chen
2023-02-23 14:43 ` Powen Kao (高伯文)
2023-02-27 22:41 ` Bart Van Assche
2023-02-22 3:04 ` [PATCH v2 4/7] scsi: ufs: core: Add hwq print for debug Po-Wen Kao
2023-02-23 10:14 ` Ziqi Chen
2023-02-23 10:49 ` Ziqi Chen
2023-02-23 14:13 ` Powen Kao (高伯文)
2023-02-27 3:14 ` Ziqi Chen
2023-02-28 2:57 ` Bao D. Nguyen
2023-03-01 2:17 ` Powen Kao (高伯文) [this message]
2023-03-01 18:50 ` Bart Van Assche
2023-03-01 18:55 ` Slade's Kernel Patch Bot
2023-02-27 22:47 ` Bart Van Assche
2023-02-22 3:04 ` [PATCH v2 5/7] scsi: ufs: core: Remove redundant check Po-Wen Kao
2023-02-22 3:33 ` Stanley Chu
2023-02-23 10:52 ` Ziqi Chen
2023-02-22 3:04 ` [PATCH v2 6/7] scsi: ufs: core: Export symbols for MTK driver module Po-Wen Kao
2023-02-22 5:19 ` Stanley Chu
2023-02-22 3:04 ` [PATCH v2 7/7] scsi: ufs: mtk-host: Add MCQ support for MTK platform Po-Wen Kao
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=f629f1b72e4859d79aac279ef3327715000e3210.camel@mediatek.com \
--to=powen.kao@mediatek.com \
--cc=Alice.Chao@mediatek.com \
--cc=Chaotian.Jing@mediatek.com \
--cc=Chun-hung.Wu@mediatek.com \
--cc=Mason.Zhang@mediatek.com \
--cc=Naomi.Chu@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=cc.chou@mediatek.com \
--cc=eddie.huang@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=jiajie.hao@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=peter.wang@mediatek.com \
--cc=quic_asutoshd@quicinc.com \
--cc=quic_cang@quicinc.com \
--cc=quic_nguyenb@quicinc.com \
--cc=quic_ziqichen@quicinc.com \
--cc=stanley.chu@mediatek.com \
--cc=wsd_upstream@mediatek.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