linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: hongwus@codeaurora.org
To: Can Guo <cang@codeaurora.org>
Cc: asutoshd@codeaurora.org, nguyenb@codeaurora.org,
	rnayak@codeaurora.org, linux-scsi@vger.kernel.org,
	kernel-team@android.com, saravanak@google.com,
	salyzyn@google.com, Sayali Lokhande <sayalil@codeaurora.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Avri Altman <avri.altman@wdc.com>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Stanley Chu <stanley.chu@mediatek.com>,
	Bean Huo <beanhuo@micron.com>,
	Bart Van Assche <bvanassche@acm.org>,
	Venkat Gopalakrishnan <venkatg@codeaurora.org>,
	Tomas Winkler <tomas.winkler@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 1/7] scsi: ufs: Flush exception event before suspend
Date: Fri, 14 Feb 2020 10:48:35 +0800	[thread overview]
Message-ID: <935eca44a8090631687a2fa298bcd595@codeaurora.org> (raw)
In-Reply-To: <1581392451-28743-2-git-send-email-cang@codeaurora.org>

On 2020-02-11 11:40, Can Guo wrote:
> From: Sayali Lokhande <sayalil@codeaurora.org>
> 
> Exception event can be raised by the device when system
> suspend is in progress. This will result in unclocked
> register access in exception event handler as clocks will
> be turned off during suspend. This change makes sure to flush
> exception event handler work in suspend before disabling
> clocks to avoid unclocked register access issue.
> 
> Signed-off-by: Sayali Lokhande <sayalil@codeaurora.org>
> Signed-off-by: Asutosh Das <asutoshd@codeaurora.org>
> Signed-off-by: Can Guo <cang@codeaurora.org>
> Reviewed-by: Bean Huo <beanhuo@micron.com>


Reviewed-by: Hongwu Su <hongwus@micron.com>

  reply	other threads:[~2020-02-14  2:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11  3:40 [PATCH v10 0/7] UFS driver general fixes bundle 4 Can Guo
2020-02-11  3:40 ` [PATCH v10 1/7] scsi: ufs: Flush exception event before suspend Can Guo
2020-02-14  2:48   ` hongwus [this message]
2020-02-11  3:40 ` [PATCH v10 2/7] scsi: ufs: set load before setting voltage in regulators Can Guo
2020-02-11  3:40 ` [PATCH v10 3/7] scsi: ufs-qcom: Adjust bus bandwidth voting and unvoting Can Guo
2020-02-11  3:40 ` [PATCH v10 4/7] scsi: ufs: Remove the check before call setup clock notify vops Can Guo
2020-02-11  3:40 ` [PATCH v10 5/7] scsi: ufs: Fix ufshcd_hold() caused scheduling while atomic Can Guo
2020-02-11  3:40 ` [PATCH v10 6/7] scsi: ufs: Add dev ref clock gating wait time support Can Guo
2020-02-11  3:40 ` [PATCH v10 7/7] scsi: ufs-qcom: Delay specific time before gate ref clk 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=935eca44a8090631687a2fa298bcd595@codeaurora.org \
    --to=hongwus@codeaurora.org \
    --cc=alim.akhtar@samsung.com \
    --cc=asutoshd@codeaurora.org \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=cang@codeaurora.org \
    --cc=jejb@linux.ibm.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=nguyenb@codeaurora.org \
    --cc=rnayak@codeaurora.org \
    --cc=salyzyn@google.com \
    --cc=saravanak@google.com \
    --cc=sayalil@codeaurora.org \
    --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).