From: Stanley Chu <stanley.chu@mediatek.com>
To: Kiwoong Kim <kwmad.kim@samsung.com>
Cc: <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>
Subject: Re: [RFC PATCH v3 1/2] ufs: introduce a callback to get info of command completion
Date: Fri, 3 Jul 2020 13:59:52 +0800 [thread overview]
Message-ID: <1593755992.3278.14.camel@mtkswgap22> (raw)
In-Reply-To: <93c364a2285a6c8eaaed6e0f68bbc8376ae7519e.1593752220.git.kwmad.kim@samsung.com>
Hi Kiwoong,
On Fri, 2020-07-03 at 14:31 +0900, Kiwoong Kim wrote:
> 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.
>
> Signed-off-by: Kiwoong Kim <kwmad.kim@samsung.com>
> ---
Please help collect all tags received in previous versions and add them
to any future new versions, for example, for this patch,
Acked-By: Stanley Chu <stanley.chu@mediatek.com>
next prev parent reply other threads:[~2020-07-03 6:00 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 ` [RFC PATCH v3 0/2] ufs: introduce callbacks to get command information Kiwoong Kim
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 [this message]
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=1593755992.3278.14.camel@mtkswgap22 \
--to=stanley.chu@mediatek.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=kwmad.kim@samsung.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