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/4] scsi: ufs: Fix broken task management command implementation
Date: Wed, 03 Jul 2013 21:22:03 +0530	[thread overview]
Message-ID: <51D448A3.1050509@codeaurora.org> (raw)
In-Reply-To: <CALMYJDv=QR8cMSoCfRgKDnyiJS6=gv7BXEPOq2vG7a1nCfvR0A@mail.gmail.com>

On 7/2/2013 9:21 PM, Santosh Y wrote:
> On Fri, Jun 28, 2013 at 5:02 PM, Sujit Reddy Thumma
> <sthumma@codeaurora.org> wrote:
>> On 6/27/2013 4:49 PM, Santosh Y wrote:
>>>>
>>>>> +       spin_lock_irqsave(host->host_lock, flags);
>>>>>          task_req_descp = hba->utmrdl_base_addr;
>>>>>          task_req_descp += free_slot;
>>>>>
>>>>> @@ -2353,38 +2387,39 @@ ufshcd_issue_tm_cmd(struct ufs_hba *hba,
>>>>>                  (struct utp_upiu_task_req *)
>>>>> task_req_descp->task_req_upiu;
>>>>>          task_req_upiup->header.dword_0 =
>>>>>                  UPIU_HEADER_DWORD(UPIU_TRANSACTION_TASK_REQ, 0,
>>>>> -                                             lrbp->lun,
>>>>> lrbp->task_tag);
>>>>> +                               lun_id, free_slot);
>>>
>>> Actually it still doesn't fix the problem. The*task tag*  used here
>>>
>>> should be unique across the SCSI/Query and Task Managment UPIUs.
>>
>>
>> I am sorry, I didn't get that. Why should it be unique across the
>> SCSI/Query? For example, if a machine supports 32 request slots and 8 task
>> management slots, then the task management command tag can be anything out
>> of 8 slots.
>>
>
> The spec(ufs 1.1) has the requirement under  '10.5.2 Basic Header
> Format'->'Task Tag'.
> Couple of devices I came across had similar behavior. The tracking of
> UPIUs --even belonging to a separate group-- seemed to be based on the
> 'task tag' value rather than 'type of UPIU'->'task tag'.

Thanks for the clarification. So to make the task tag unique we should 
do something like below:

@@ -2940,9 +2941,10 @@ static int ufshcd_issue_tm_cmd(struct ufs_hba 
*hba, int lun_id, int task_id,
         /* Configure task request UPIU */
         task_req_upiup =
                 (struct utp_upiu_task_req *) task_req_descp->task_req_upiu;
+       task_tag = hba->nutrs + free_slot;
         task_req_upiup->header.dword_0 =
                 UPIU_HEADER_DWORD(UPIU_TRANSACTION_TASK_REQ, 0,
-                               lun_id, free_slot);
+                               lun_id, task_tag);

Will this work for the devices you came across?


-- 
Regards,
Sujit

  reply	other threads:[~2013-07-03 15:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 14:30 [PATCH 0/4] scsi: ufs: Improve UFS error handling Sujit Reddy Thumma
2013-06-13 14:30 ` [PATCH 1/4] scsi: ufs: Fix broken task management command implementation Sujit Reddy Thumma
2013-06-27 11:19   ` Santosh Y
2013-06-28 11:32     ` Sujit Reddy Thumma
2013-07-02 15:51       ` Santosh Y
2013-07-03 15:52         ` Sujit Reddy Thumma [this message]
2013-07-03 16:23           ` Santosh Y
2013-07-03 16:42             ` Sujit Reddy Thumma
2013-06-13 14:30 ` [PATCH 2/4] scsi: ufs: Fix hardware race conditions while aborting a command Sujit Reddy Thumma
2013-06-13 14:30 ` [PATCH 3/4] scsi: ufs: Fix device and host reset methods Sujit Reddy Thumma
2013-06-13 14:31 ` [PATCH 4/4] scsi: ufs: Improve UFS fatal error handling Sujit Reddy Thumma
  -- strict thread matches above, loose matches on Subject: below --
2013-08-14 17:10 [PATCH 0/4] scsi: ufs: TM, fatal-error handling and other fixes Santosh Y
2013-08-14 17:10 ` [PATCH 1/4] scsi: ufs: Fix broken task management command implementation Santosh Y

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=51D448A3.1050509@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).