From: Can Guo <cang@codeaurora.org>
To: Avri Altman <Avri.Altman@wdc.com>
Cc: "moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
Stanley Chu <stanley.chu@mediatek.com>,
rnayak@codeaurora.org, saravanak@google.com,
linux-scsi@vger.kernel.org,
Venkat Gopalakrishnan <venkatg@codeaurora.org>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
nguyenb@codeaurora.org, open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
salyzyn@google.com, Alim Akhtar <alim.akhtar@samsung.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Tomas Winkler <tomas.winkler@intel.com>,
Bean Huo <beanhuo@micron.com>,
kernel-team@android.com, Bart Van Assche <bvanassche@acm.org>,
hongwus@codeaurora.org, asutoshd@codeaurora.org
Subject: Re: [PATCH 5/7] scsi: ufs: Fix ufshcd_hold() caused scheduling while atomic
Date: Mon, 10 Feb 2020 10:00:40 +0800 [thread overview]
Message-ID: <c89901f4e7f2c7200d1aefe55e3c9fb4@codeaurora.org> (raw)
In-Reply-To: <MN2PR04MB69919F988AA4F1B7BD36408BFC1E0@MN2PR04MB6991.namprd04.prod.outlook.com>
On 2020-02-09 15:48, Avri Altman wrote:
> You didn't address any of my comments to this patch.
>
> Thanks,
> Avri
Replied in that thread.
Thanks,
Can Guo.
>>
>> The async version of ufshcd_hold(async == true), which is only called
>> in queuecommand path as for now, is expected to work in atomic
>> context,
>> thus it should not sleep or schedule out. When it runs into the
>> condition
>> that clocks are ON but link is still in hibern8 state, it should bail
>> out
>> without flushing the clock ungate work.
>>
>> Signed-off-by: Can Guo <cang@codeaurora.org>
>> Reviewed-by: Hongwu Su <hongwus@codeaurora.org>
>> Reviewed-by: Asutosh Das <asutoshd@codeaurora.org>
>> Reviewed-by: Bean Huo <beanhuo@micron.com>
>> Reviewed-by: Stanley Chu <stanley.chu@mediatek.com>
>>
>> diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
>> index bbc2607..e8f7f9d 100644
>> --- a/drivers/scsi/ufs/ufshcd.c
>> +++ b/drivers/scsi/ufs/ufshcd.c
>> @@ -1518,6 +1518,11 @@ int ufshcd_hold(struct ufs_hba *hba, bool
>> async)
>> */
>> if (ufshcd_can_hibern8_during_gating(hba) &&
>> ufshcd_is_link_hibern8(hba)) {
>> + if (async) {
>> + rc = -EAGAIN;
>> + hba->clk_gating.active_reqs--;
>> + break;
>> + }
>> spin_unlock_irqrestore(hba->host->host_lock,
>> flags);
>> flush_work(&hba->clk_gating.ungate_work);
>> spin_lock_irqsave(hba->host->host_lock,
>> flags);
>> --
>> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
>> Forum,
>> a Linux Foundation Collaborative Project
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-02-10 2:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1581123030-12023-1-git-send-email-cang@codeaurora.org>
2020-02-08 0:50 ` [PATCH 2/7] scsi: ufs: set load before setting voltage in regulators Can Guo
2020-02-08 0:50 ` [PATCH 3/7] scsi: ufs: Remove the check before call setup clock notify vops Can Guo
2020-02-08 0:50 ` [PATCH 5/7] scsi: ufs: Fix ufshcd_hold() caused scheduling while atomic Can Guo
2020-02-09 7:48 ` Avri Altman
2020-02-10 2:00 ` Can Guo [this message]
2020-02-08 0:50 ` [PATCH 6/7] scsi: ufs: Add dev ref clock gating wait time support 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=c89901f4e7f2c7200d1aefe55e3c9fb4@codeaurora.org \
--to=cang@codeaurora.org \
--cc=Avri.Altman@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=hongwus@codeaurora.org \
--cc=jejb@linux.ibm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=nguyenb@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=salyzyn@google.com \
--cc=saravanak@google.com \
--cc=stanley.chu@mediatek.com \
--cc=tomas.winkler@intel.com \
--cc=venkatg@codeaurora.org \
/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).