From: Kiwoong Kim <kwmad.kim@samsung.com>
To: linux-scsi@vger.kernel.org, alim.akhtar@samsung.com,
avri.altman@wdc.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, beanhuo@micron.com,
asutoshd@codeaurora.org, cang@codeaurora.org, bvanassche@acm.org,
grant.jung@samsung.com, sc.suh@samsung.com, hy50.seo@samsung.com,
sh425.lee@samsung.com
Cc: Kiwoong Kim <kwmad.kim@samsung.com>
Subject: [RFC PATCH v5 0/3] ufs: exynos: introduce the way to get cmd info
Date: Sat, 11 Jul 2020 15:57:42 +0900 [thread overview]
Message-ID: <cover.1594450408.git.kwmad.kim@samsung.com> (raw)
In-Reply-To: CGME20200711070541epcas2p47678883840df461f649becfc73792da5@epcas2p4.samsung.com
v4 -> v5
Rebased on Stanley's patch (scsi: ufs: Fix and simplify ..
Change cmd history print order
rename config to SCSI_UFS_EXYNOS_DBG
feature functions in ufs-exynos-dbg.c by SCSI_UFS_EXYNOS_DBG
v3 -> v4
seperate respective implementations of the callbacks
change the location of compl_xfer_req related stuffs
fix null pointer access
v2 -> v3
fix build errors
v1 -> v2
change callbacks
allocate memory for ufs_s_dbg_mgr dynamically, not static way
Kiwoong Kim (3):
ufs: introduce a callback to get info of command completion
ufs: exynos: introduce command history
ufs: exynos: implement dbg_register_dump
drivers/scsi/ufs/Kconfig | 14 +++
drivers/scsi/ufs/Makefile | 1 +
drivers/scsi/ufs/ufs-exynos-dbg.c | 197 ++++++++++++++++++++++++++++++++++++++
drivers/scsi/ufs/ufs-exynos-if.h | 17 ++++
drivers/scsi/ufs/ufs-exynos.c | 39 ++++++++
drivers/scsi/ufs/ufs-exynos.h | 35 +++++++
drivers/scsi/ufs/ufshcd.c | 1 +
drivers/scsi/ufs/ufshcd.h | 8 ++
8 files changed, 312 insertions(+)
create mode 100644 drivers/scsi/ufs/ufs-exynos-dbg.c
create mode 100644 drivers/scsi/ufs/ufs-exynos-if.h
--
2.7.4
next parent reply other threads:[~2020-07-11 7:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200711070541epcas2p47678883840df461f649becfc73792da5@epcas2p4.samsung.com>
2020-07-11 6:57 ` Kiwoong Kim [this message]
[not found] ` <CGME20200711070543epcas2p28a42f8386624ecaede5329e035e5e1a9@epcas2p2.samsung.com>
2020-07-11 6:57 ` [RFC PATCH v5 1/3] ufs: introduce a callback to get info of command completion Kiwoong Kim
[not found] ` <CGME20200711070544epcas2p4d3a75d2f56b8162c09efa0eeaf012fa2@epcas2p4.samsung.com>
2020-07-11 6:57 ` [RFC PATCH v5 2/3] ufs: exynos: introduce command history Kiwoong Kim
2020-07-12 1:55 ` Alim Akhtar
2020-07-13 4:33 ` Kiwoong Kim
[not found] ` <CGME20200711070544epcas2p10291ef069c92d54a7cb8a6b7e0eb09a1@epcas2p1.samsung.com>
2020-07-11 6:57 ` [RFC PATCH v5 3/3] ufs: exynos: implement dbg_register_dump Kiwoong Kim
2020-07-12 1:58 ` [RFC PATCH v5 0/3] ufs: exynos: introduce the way to get cmd info Alim Akhtar
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=cover.1594450408.git.kwmad.kim@samsung.com \
--to=kwmad.kim@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=grant.jung@samsung.com \
--cc=hy50.seo@samsung.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sc.suh@samsung.com \
--cc=sh425.lee@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;
as well as URLs for NNTP newsgroup(s).