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 v3 0/2] ufs: introduce callbacks to get command information
Date: Fri, 3 Jul 2020 14:31:03 +0900 [thread overview]
Message-ID: <cover.1593752220.git.kwmad.kim@samsung.com> (raw)
In-Reply-To: CGME20200703053852epcas2p47779aeac8c01a2b94596fdd9e660fe69@epcas2p4.samsung.com
v2 -> v3
fix build errors
v1 -> v2
change callbacks
allocate memory for ufs_s_dbg_mgr dynamically, not static way
Some SoC specific might need command history for
various reasons, such as stacking command contexts
in system memory to check for debugging in the future
or scaling some DVFS knobs to boost IO throughput.
What you would do with the information could be
variant per SoC vendor.
Kiwoong Kim (2):
ufs: introduce a callback to get info of command completion
exynos-ufs: implement dbg_register_dump and compl_xfer_req
drivers/scsi/ufs/Kconfig | 14 +++
drivers/scsi/ufs/Makefile | 2 +-
drivers/scsi/ufs/ufs-exynos-dbg.c | 202 ++++++++++++++++++++++++++++++++++++++
drivers/scsi/ufs/ufs-exynos-if.h | 17 ++++
drivers/scsi/ufs/ufs-exynos.c | 63 +++++++++++-
drivers/scsi/ufs/ufs-exynos.h | 13 +++
drivers/scsi/ufs/ufshcd.c | 2 +
drivers/scsi/ufs/ufshcd.h | 8 ++
8 files changed, 318 insertions(+), 3 deletions(-)
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-03 5:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200703053852epcas2p47779aeac8c01a2b94596fdd9e660fe69@epcas2p4.samsung.com>
2020-07-03 5:31 ` Kiwoong Kim [this message]
2020-07-03 5:31 ` [RFC PATCH v3 1/2] ufs: introduce a callback to get info of command completion Kiwoong Kim
2020-07-03 5:59 ` Stanley Chu
2020-07-03 7:08 ` Kiwoong Kim
2020-07-05 11:37 ` Avri Altman
2020-07-06 6:41 ` Kiwoong Kim
2020-07-03 5:31 ` [RFC PATCH v3 2/2] exynos-ufs: implement dbg_register_dump and compl_xfer_req Kiwoong Kim
2020-07-05 11:38 ` Avri Altman
2020-07-06 6:41 ` Kiwoong Kim
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.1593752220.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