From: "Martin K. Petersen" <martin.petersen@oracle•com>
To: Stanley Chu <stanley.chu@mediatek•com>
Cc: sthumma@codeaurora•org, linux-scsi@vger•kernel.org,
martin.petersen@oracle•com, marc.w.gonzalez@free•fr,
subhashj@codeaurora•org, chun-hung.wu@mediatek•com,
kuohong.wang@mediatek•com, peter.wang@mediatek•com,
evgreen@chromium•org, avri.altman@wdc•com,
linux-mediatek@lists•infradead.org, ygardi@codeaurora•org,
alim.akhtar@samsung•com, andy.teng@mediatek•com,
matthias.bgg@gmail•com, stable@vger•kernel.org,
pedrom.sousa@synopsys•com, linux-arm-kernel@lists•infradead.org,
beanhuo@micron•com
Subject: Re: [PATCH v2] scsi: ufs: Avoid runtime suspend possibly being blocked forever
Date: Tue, 18 Jun 2019 22:51:10 -0400 [thread overview]
Message-ID: <yq18stywan5.fsf@oracle.com> (raw)
In-Reply-To: <1560352745-24681-1-git-send-email-stanley.chu@mediatek.com> (Stanley Chu's message of "Wed, 12 Jun 2019 23:19:05 +0800")
Stanley,
> UFS runtime suspend can be triggered after pm_runtime_enable()
> is invoked in ufshcd_pltfrm_init(). However if the first runtime
> suspend is triggered before binding ufs_hba structure to ufs
> device structure via platform_set_drvdata(), then UFS runtime
> suspend will be no longer triggered in the future because its
> dev->power.runtime_error was set in the first triggering and does
> not have any chance to be cleared.
Applied to 5.2/scsi-fixes. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-06-19 2:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 15:19 [PATCH v2] scsi: ufs: Avoid runtime suspend possibly being blocked forever Stanley Chu
2019-06-13 8:09 ` Avri Altman
2019-06-19 2:51 ` 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=yq18stywan5.fsf@oracle.com \
--to=martin.petersen@oracle$(echo .)com \
--cc=alim.akhtar@samsung$(echo .)com \
--cc=andy.teng@mediatek$(echo .)com \
--cc=avri.altman@wdc$(echo .)com \
--cc=beanhuo@micron$(echo .)com \
--cc=chun-hung.wu@mediatek$(echo .)com \
--cc=evgreen@chromium$(echo .)org \
--cc=kuohong.wang@mediatek$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-mediatek@lists$(echo .)infradead.org \
--cc=linux-scsi@vger$(echo .)kernel.org \
--cc=marc.w.gonzalez@free$(echo .)fr \
--cc=matthias.bgg@gmail$(echo .)com \
--cc=pedrom.sousa@synopsys$(echo .)com \
--cc=peter.wang@mediatek$(echo .)com \
--cc=stable@vger$(echo .)kernel.org \
--cc=stanley.chu@mediatek$(echo .)com \
--cc=sthumma@codeaurora$(echo .)org \
--cc=subhashj@codeaurora$(echo .)org \
--cc=ygardi@codeaurora$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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