From: Stanley Chu <stanley.chu@mediatek.com>
To: <linux-scsi@vger.kernel.org>, <martin.petersen@oracle.com>,
<avri.altman@wdc.com>, <alim.akhtar@samsung.com>,
<jejb@linux.ibm.com>, <asutoshd@codeaurora.org>
Cc: <beanhuo@micron.com>, <cang@codeaurora.org>,
<matthias.bgg@gmail.com>, <bvanassche@acm.org>,
<linux-mediatek@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <kuohong.wang@mediatek.com>,
<peter.wang@mediatek.com>, <chun-hung.wu@mediatek.com>,
<andy.teng@mediatek.com>, <cc.chou@mediatek.com>,
<chaotian.jing@mediatek.com>,
Stanley Chu <stanley.chu@mediatek.com>
Subject: [PATCH v2 0/3] scsi: ufs: Export UFS debugging dump for vendors
Date: Mon, 15 Jun 2020 22:48:02 +0800 [thread overview]
Message-ID: <20200615144805.6921-1-stanley.chu@mediatek.com> (raw)
Hi,
This series creates an unified entry function for UFS debugging information dump, and exports it to vendors to help debugging.
In the same time, do a small cleanup in ufshcd_make_hba_operational().
v1 -> v2:
- Fix incorrect returned value in patch[3]'s ufs_mtk_link_set_hpm()
Stanley Chu (3):
scsi: ufs: Remove redundant label "out" in
ufshcd_make_hba_operational()
scsi: ufs: Manage and export UFS debugging information dump
scsi: ufs-mediatek: Print host information for failed supsend and
resume
drivers/scsi/ufs/ufs-mediatek.c | 16 +++++++----
drivers/scsi/ufs/ufshcd.c | 51 +++++++++++++++++++--------------
drivers/scsi/ufs/ufshcd.h | 8 ++++++
3 files changed, 47 insertions(+), 28 deletions(-)
--
2.18.0
next reply other threads:[~2020-06-15 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 14:48 Stanley Chu [this message]
2020-06-15 14:48 ` [PATCH v2 1/3] scsi: ufs: Remove redundant label "out" in ufshcd_make_hba_operational() Stanley Chu
2020-06-15 14:48 ` [PATCH v2 2/3] scsi: ufs: Manage and export UFS debugging information dump Stanley Chu
2020-06-15 14:48 ` [PATCH v2 3/3] scsi: ufs-mediatek: Print host information for failed supsend and resume Stanley Chu
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=20200615144805.6921-1-stanley.chu@mediatek.com \
--to=stanley.chu@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=andy.teng@mediatek.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=cc.chou@mediatek.com \
--cc=chaotian.jing@mediatek.com \
--cc=chun-hung.wu@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=kuohong.wang@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 \
/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;
as well as URLs for NNTP newsgroup(s).