public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sujit Reddy Thumma <sthumma@codeaurora.org>
To: Santosh Y <santoshsy@gmail.com>
Cc: Vinayak Holikatti <vinholikatti@gmail.com>,
	"James E.J. Bottomley" <JBottomley@parallels.com>,
	linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] scsi: ufs: Add support for sending NOP OUT UPIU
Date: Thu, 02 May 2013 17:01:18 +0530	[thread overview]
Message-ID: <51824E86.6010805@codeaurora.org> (raw)
In-Reply-To: <CALMYJDut2=gwVsNxfeEM5mR2K9uJ0nMiV2y=xu3WZEUpfN-z7w@mail.gmail.com>

On 5/2/2013 12:57 PM, Santosh Y wrote:
>> +
>> +/**
>> + * ufshcd_validate_dev_connection() - Check device connection status
>> + * @hba: per-adapter instance
>> + *
>> + * Send NOP OUT UPIU and wait for NOP IN response to check whether the
>> + * device Transport Protocol (UTP) layer is ready after a reset.
>> + * If the UTP layer at the device side is not initialized, it may
>> + * not respond with NOP IN UPIU within timeout of %NOP_OUT_TIMEOUT
>> + * and we retry sending NOP OUT for %NOP_OUT_RETRIES iterations.
>> + */
>> +static int ufshcd_validate_dev_connection(struct ufs_hba *hba)
>> +{
>> +       int err;
>> +       struct ufshcd_lrb *lrbp;
>> +       unsigned long timeout;
>> +       unsigned long flags;
>> +       struct completion wait;
>> +       int retries = NOP_OUT_RETRIES;
>> +
>> +retry:
>> +       spin_lock_irqsave(hba->host->host_lock, flags);
>> +       lrbp = &hba->lrb[INTERNAL_CMD_TAG];
>> +       init_completion(&wait);
>> +
>> +       err = ufshcd_compose_nop_out_upiu(hba, lrbp);
>> +       if (err)
>> +               goto may_retry;
>> +
>> +       lrbp->completion = &wait;
>> +       ufshcd_send_command(hba, INTERNAL_CMD_TAG);
>> +       spin_unlock_irqrestore(hba->host->host_lock, flags);
>> +
>> +       timeout = wait_for_completion_timeout(
>> +                       &wait, msecs_to_jiffies(NOP_OUT_TIMEOUT));
>> +
>> +       spin_lock_irqsave(hba->host->host_lock, flags);
>> +       if (timeout > 0) {
>> +               int ocs;
>> +
>> +               ocs = ufshcd_get_tr_ocs(lrbp);
>> +               switch (ocs) {
>> +               case OCS_SUCCESS:
>> +                       goto out;
>> +               default:
>> +                       dev_dbg(hba->dev, "%s: OCS error %d\n", __func__, ocs);
>> +                       err = -EIO;
>> +                       goto may_retry;
>> +               }
>> +       } else {
>> +               u32 reg;
>> +
>> +               err = -ETIMEDOUT;
>> +
>> +               /* clear outstanding transaction before retry */
>> +               ufshcd_utrl_clear(hba, INTERNAL_CMD_TAG);
>> +               __clear_bit(INTERNAL_CMD_TAG, &hba->outstanding_reqs);
>> +
>> +               /* poll for max. 1 sec to clear door bell register by h/w */
>> +               spin_unlock_irqrestore(hba->host->host_lock, flags);
>> +               if (readl_poll_timeout(
>> +                               hba->mmio_base + REG_UTP_TRANSFER_REQ_DOOR_BELL,
>> +                               reg, !(reg & INTERNAL_CMD_TAG), 1000, 1000))
>
> Condition is always true here, change it to !(reg & (1 << INTERNAL_CMD_TAG)).

Good catch. I will update.

>
>> +                       retries = 0;
>> +               spin_lock_irqsave(hba->host->host_lock, flags);
>> +               goto may_retry;
>> +       }
>> +
>
>
>

-- 
Regards,
Sujit

      reply	other threads:[~2013-05-02 11:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 14:14 [PATCH 1/1] scsi: ufs: Add support for sending NOP OUT UPIU Sujit Reddy Thumma
2013-05-02  7:27 ` Santosh Y
2013-05-02 11:31   ` Sujit Reddy Thumma [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=51824E86.6010805@codeaurora.org \
    --to=sthumma@codeaurora.org \
    --cc=JBottomley@parallels.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@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