linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sujit Reddy Thumma <sthumma@codeaurora.org>
To: Santosh Y <santoshsy@gmail.com>
Cc: Vinayak Holikatti <vinholikatti@gmail.com>,
	linux-scsi@vger.kernel.org, JBottomley@parallels.com,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/2] scsi: ufs: Add support for host assisted background operations
Date: Fri, 28 Jun 2013 17:31:35 +0530	[thread overview]
Message-ID: <51CD7B1F.3020200@codeaurora.org> (raw)
In-Reply-To: <CALMYJDuzvMQxNa_715odFs-jg8q5aEtpKSE5Dyve6wrqD8TwFg@mail.gmail.com>

On 6/26/2013 11:06 PM, Santosh Y wrote:
>> +/**
>> >   * ufshcd_memory_alloc - allocate memory for host memory space data
>> >structures
>> >   * @hba: per adapter instance
>> >   *
>> >@@ -1803,6 +1904,9 @@ ufshcd_transfer_rsp_status(struct ufs_hba *hba,
>> >struct ufshcd_lrb *lrbp)
>> >                          */
>> >                         scsi_status = result & MASK_SCSI_STATUS;
>> >                         result = ufshcd_scsi_cmd_status(lrbp,
>> >scsi_status);
>> >+
>> >+                       if (ufshcd_is_exception_event(lrbp->ucd_rsp_ptr))
>                                  ^^^^^
> This condition will not satisfy until a runtime suspend/resume cycle
> completes. Is there any specific reason it is only being enabled in
> runtime-resume routine?
> As the fBackgroundOpsEn = 1 by default, shouldn't the sequence be 1.
> ufshcd_disable_auto_bkops() 2. ufshcd_enable_ee() during the startup.
>

According to the specification, the host should put in all measures to 
ensure that the device doesn't enter into URGENT_BKOPS need because the 
device may not operate optimally in that case. If your sequence is used 
then we expect a case where URGENT_BKOPS is needed if the runtime PM is 
disabled or prohibited soon after startup.

We wouldn't want to disable auto bkops by default without knowing that 
the runtime PM is enabled, since the device/host/software idleness is 
determined by runtime PM operation as explained in the commit text.

-- 
Regards,
Sujit

  reply	other threads:[~2013-06-28 12:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 14:20 [PATCH 0/2] scsi: ufs: Add support to control UFS device background operations Sujit Reddy Thumma
2013-06-13 14:20 ` [PATCH 1/2] scsi: ufs: Add support for host assisted " Sujit Reddy Thumma
2013-06-26 17:36   ` Santosh Y
2013-06-28 12:01     ` Sujit Reddy Thumma [this message]
2013-06-13 14:20 ` [PATCH 2/2] scsi: ufs: Add runtime PM helpers for UFS host driver Sujit Reddy Thumma

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=51CD7B1F.3020200@codeaurora.org \
    --to=sthumma@codeaurora.org \
    --cc=JBottomley@parallels.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=santoshsy@gmail.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).