Linux SCSI subsystem development
 help / color / mirror / Atom feed
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>
Subject: Re: [RFC PATCH v2 0/2] ufs: introduce callbacks to get command information
Date: Thu, 2 Jul 2020 10:49:51 +0800	[thread overview]
Message-ID: <1593658191.3278.7.camel@mtkswgap22> (raw)
In-Reply-To: <cover.1593657314.git.kwmad.kim@samsung.com>

Hi Kiwoong,

On Thu, 2020-07-02 at 11:38 +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.
> 
> Kiwoong Kim (2):
>   ufs: introduce a callback to get info of command completion
>   exynos-ufs: implement dbg_register_dump and compl_xfer_req

Thanks for the update!

Would you please elaborate the change log in cover letter for easier
review in the future?

Thanks,
Stanley Chu



  parent reply	other threads:[~2020-07-02  2:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200702024556epcas2p41b15bb9fb91884435a2cb8711273d29f@epcas2p4.samsung.com>
2020-07-02  2:38 ` [RFC PATCH v2 0/2] ufs: introduce callbacks to get command information Kiwoong Kim
2020-07-02  2:38   ` [RFC PATCH v2 1/2] ufs: introduce a callback to get info of command completion Kiwoong Kim
2020-07-02  5:10     ` Stanley Chu
2020-07-02  2:38   ` [RFC PATCH v2 2/2] exynos-ufs: implement dbg_register_dump and compl_xfer_req Kiwoong Kim
2020-07-02  2:49   ` Stanley Chu [this message]
2020-07-02  2:55     ` [RFC PATCH v2 0/2] ufs: introduce callbacks to get command information 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=1593658191.3278.7.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=jejb@linux.ibm.com \
    --cc=kwmad.kim@samsung.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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