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>
Cc: <beanhuo@micron.com>, <asutoshd@codeaurora.org>,
<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>, <chaotian.jing@mediatek.com>,
<cc.chou@mediatek.com>, <jiajie.hao@mediatek.com>,
<alice.chao@mediatek.com>, <huadian.liu@mediatek.com>,
Stanley Chu <stanley.chu@mediatek.com>
Subject: [PATCH v5 0/4] scsi: ufs: Refine error history and introduce event_notify vop
Date: Sat, 5 Dec 2020 19:58:57 +0800 [thread overview]
Message-ID: <20201205115901.26815-1-stanley.chu@mediatek.com> (raw)
Hi,
This series refines error history functions and introduces a new event_notify vop to allow vendor to get notification of important events.
Changes since v4:
- Seperate patch sets according to Avri's suggestion
Changes since v3:
- Fix build warning in patch [8/8]
Changes since v2:
- Add patches for vop cleanups
- Introduce phy_initialization helper and replace direct invoking in ufs-cdns and ufs-dwc by the helper
- Introduce event_notify vop implemntation in ufs-mediatek
Changes since v1:
- Change notify_event() to event_notify() to follow vop naming covention
Stanley Chu (4):
scsi: ufs: Add error history for abort event in UFS Device W-LUN
scsi: ufs: Refine error history functions
scsi: ufs: Introduce event_notify variant function
scsi: ufs-mediatek: Introduce event_notify implementation
drivers/scsi/ufs/ufs-mediatek-trace.h | 37 ++++++++
drivers/scsi/ufs/ufs-mediatek.c | 12 +++
drivers/scsi/ufs/ufshcd.c | 122 +++++++++++++++-----------
drivers/scsi/ufs/ufshcd.h | 82 ++++++++---------
4 files changed, 161 insertions(+), 92 deletions(-)
create mode 100644 drivers/scsi/ufs/ufs-mediatek-trace.h
--
2.18.0
next reply other threads:[~2020-12-05 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 11:58 Stanley Chu [this message]
2020-12-05 11:58 ` [PATCH v5 1/4] scsi: ufs: Add error history for abort event in UFS Device W-LUN Stanley Chu
2020-12-05 11:58 ` [PATCH v5 2/4] scsi: ufs: Refine error history functions Stanley Chu
2020-12-05 11:59 ` [PATCH v5 3/4] scsi: ufs: Introduce event_notify variant function Stanley Chu
2020-12-05 11:59 ` [PATCH v5 4/4] scsi: ufs-mediatek: Introduce event_notify implementation Stanley Chu
2020-12-07 22:53 ` [PATCH v5 0/4] scsi: ufs: Refine error history and introduce event_notify vop Martin K. Petersen
2020-12-09 17:23 ` Martin K. Petersen
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=20201205115901.26815-1-stanley.chu@mediatek.com \
--to=stanley.chu@mediatek.com \
--cc=alice.chao@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=huadian.liu@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=jiajie.hao@mediatek.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).