MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 17 Oct 2016 17:13:56 -0700
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
In-Reply-To: <yq137jyk68k.fsf@sermon.lab.mkp.net>
References: <1476227759-22389-1-git-send-email-subhashj@codeaurora.org>
 <yq137jyk68k.fsf@sermon.lab.mkp.net>
Message-ID: <8edb1a0aaa886ffc80564117a020f490@codeaurora.org>
User-Agent: Roundcube Webmail/1.2.1
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1036
Lines: 25

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