From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: <peter.wang@mediatek.com>
Cc: <stanley.chu@mediatek.com>, <linux-scsi@vger.kernel.org>,
<martin.petersen@oracle.com>, <avri.altman@wdc.com>,
<alim.akhtar@samsung.com>, <jejb@linux.ibm.com>,
<wsd_upstream@mediatek.com>, <linux-mediatek@lists.infradead.org>,
<chun-hung.wu@mediatek.com>, <alice.chao@mediatek.com>,
<cc.chou@mediatek.com>, <chaotian.jing@mediatek.com>,
<jiajie.hao@mediatek.com>, <powen.kao@mediatek.com>,
<qilin.tan@mediatek.com>, <lin.gui@mediatek.com>,
<tun-yu.yu@mediatek.com>, <eddie.huang@mediatek.com>,
<naomi.chu@mediatek.com>
Subject: Re: [PATCH v1] ufs: core: remove dev cmd clock scaling busy
Date: Mon, 09 Oct 2023 21:37:47 -0400 [thread overview]
Message-ID: <yq1wmvvntpg.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20231004062454.29165-1-peter.wang@mediatek.com> (peter wang's message of "Wed, 4 Oct 2023 14:24:54 +0800")
Peter,
> If dev command timeout, clk_scaling.active_reqs is not decrease and
> cause clock scaling framework abnormal. But it is complicated to
> handle different dev command timeout case in legacy mode or mcq mode.
> Besides, dev cmd is rare used and busy time is short. So remove clock
> scaling busy window for dev cmd is properly. Same as uic or tm cmd
> which doesn't update busy window too.
Applied to 6.7/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2023-10-10 1:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 6:24 [PATCH v1] ufs: core: remove dev cmd clock scaling busy peter.wang
2023-10-04 6:37 ` Stanley Chu
2023-10-10 1:37 ` Martin K. Petersen [this message]
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=yq1wmvvntpg.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=alice.chao@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=cc.chou@mediatek.com \
--cc=chaotian.jing@mediatek.com \
--cc=chun-hung.wu@mediatek.com \
--cc=eddie.huang@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=jiajie.hao@mediatek.com \
--cc=lin.gui@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=naomi.chu@mediatek.com \
--cc=peter.wang@mediatek.com \
--cc=powen.kao@mediatek.com \
--cc=qilin.tan@mediatek.com \
--cc=stanley.chu@mediatek.com \
--cc=tun-yu.yu@mediatek.com \
--cc=wsd_upstream@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