From: Subhash Jadavani <subhashj@codeaurora.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: vinholikatti@gmail.com, jejb@linux.vnet.ibm.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] scsi: ufs: fix race between clock gating and devfreq scaling work
Date: Mon, 17 Oct 2016 17:13:56 -0700 [thread overview]
Message-ID: <8edb1a0aaa886ffc80564117a020f490@codeaurora.org> (raw)
In-Reply-To: <yq137jyk68k.fsf@sermon.lab.mkp.net>
On 2016-10-14 13:47, Martin K. Petersen wrote:
>>>>>> "Subhash" == Subhash Jadavani <subhashj@codeaurora.org> writes:
>
> Subhash> UFS devfreq clock scaling work may require clocks to be ON if
> Subhash> it need to execute some UFS commands hence it may request for
> Subhash> clock hold before issuing the command. But if UFS clock gating
> Subhash> work is already running in parallel, ungate work would end up
> Subhash> waiting for the clock gating work to finish and as clock
> gating
> Subhash> work would also wait for the clock scaling work to finish, we
> Subhash> would enter in deadlock state. Here is the call trace during
> Subhash> this deadlock state:
>
> Somebody from the UFS camp, please review!
As there was no review so far, i have moved this patch as first patch in
the new UFS bug fixes patch series ([PATCH v1 00/11] scsi: ufs: bug
fixes patch series #1) sent by me today.
Thanks,
Subhash
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2016-10-18 0:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 23:15 [RESEND PATCH] scsi: ufs: fix race between clock gating and devfreq scaling work Subhash Jadavani
2016-10-14 20:47 ` Martin K. Petersen
2016-10-18 0:13 ` Subhash Jadavani [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=8edb1a0aaa886ffc80564117a020f490@codeaurora.org \
--to=subhashj@codeaurora.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=vinholikatti@gmail.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).