From: Bart Van Assche <bvanassche@acm.org>
To: Kiwoong Kim <kwmad.kim@samsung.com>,
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,
grant.jung@samsung.com, sc.suh@samsung.com, hy50.seo@samsung.com,
sh425.lee@samsung.com
Subject: Re: [RFC PATCH v1] ufs: introduce async ufs interface initialization
Date: Sat, 18 Jul 2020 13:38:43 -0700 [thread overview]
Message-ID: <8565af37-3d2c-fac9-94f7-0d9fc25c4d38@acm.org> (raw)
In-Reply-To: <1593678039-139543-1-git-send-email-kwmad.kim@samsung.com>
On 2020-07-02 01:20, Kiwoong Kim wrote:
> When you set uic_link_state during sleep statae to
> UIC_LINK_OFF_STATE, UFS driver does interface initialization
> that is a series of some steps including fDeviceInit and thus,
> You might feel that its latency is a little bit longer.
>
> This patch is run it asynchronously to reduce system wake-up time.
Device drivers like UFS should only perform tasks that are specific to
the supported device(s). Asynchronous resume from a sleep state is a
mechanism that may also benefit other device drivers. Please work with
the maintainers of the power management subsystem (Rafael J. Wysocki and
Pavel Machek) to integrate support for this feature in the kernel power
management subsystem. The kernel power management subsystem exists in
the directory kernel/power.
Thanks,
Bart.
next prev parent reply other threads:[~2020-07-18 20:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200702082826epcas2p2face6d1689c2f5efc1dcdb53c19804b8@epcas2p2.samsung.com>
2020-07-02 8:20 ` [RFC PATCH v1] ufs: introduce async ufs interface initialization Kiwoong Kim
2020-07-07 6:05 ` Avri Altman
2020-07-07 6:09 ` Kiwoong Kim
2020-07-07 6:50 ` Grant Jung
2020-07-15 8:35 ` Kiwoong Kim
2020-07-18 20:38 ` Bart Van Assche [this message]
2020-07-19 0:27 ` Can Guo
2020-07-19 5:16 ` Can Guo
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=8565af37-3d2c-fac9-94f7-0d9fc25c4d38@acm.org \
--to=bvanassche@acm.org \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--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;
as well as URLs for NNTP newsgroup(s).