From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Akinobu Mita <akinobu.mita@gmail.com>,
Joao Pinto <Joao.Pinto@synopsys.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Yaniv Gardi <ygardi@codeaurora.org>,
Gilad Broner <gbroner@codeaurora.org>,
Subhash Jadavani <subhashj@codeaurora.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
CARLOS.PALMINHA@synopsys.com
Subject: Re: [PATCH] add driver for DesignWare UFS Host Controller
Date: Thu, 28 Jan 2016 17:00:28 +0000 [thread overview]
Message-ID: <56AA492C.80707@synopsys.com> (raw)
In-Reply-To: <CAC5umyhHnAMqBfkPoJfZ7qhw89-0AqFQG70-XnyRzQk1Yxb=6Q@mail.gmail.com>
Hi Akinobu,
Thanks for the tip!
Joao
On 1/28/2016 12:35 PM, Akinobu Mita wrote:
> Hi Joao,
>
> 2016-01-28 2:04 GMT+09:00 Joao Pinto <Joao.Pinto@synopsys.com>:
>> - NOP_OUT is failing with OCS = 0x7
>>
>> The OCS value is calculated in ufshcd_get_tr_ocs() in ufshcd.c.
>> I made a dump of the UTRD pointer where we can check the status = 7 ([2]).
>>
>> UTRD at: 7007c3e0
>> @0000 [0]:21000000
>> @0004 [1]:93936a6a
>> @0008 [2]:00000007
>> @000c [3]:93936a6a
>> @0010 [4]:9f317400
>> @0014 [5]:00000000
>> @0018 [6]:00800080
>> @001c [7]:01006a6a
>>
>> Did anyone have the same problem? Any hints to overcome this issue?
>
> I have seen similar problem when using UFS 2.0 controller.
>
> The ufs driver currently doesn't set correct command type field in
> UTP transfer request descriptor (bit 31:28 in DW0) for UFS 2.0
> controller. I checked that your DesignWare UFS driver handles it
> correctly, so please try with that change.
>
next prev parent reply other threads:[~2016-01-28 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 17:27 [PATCH] add driver for DesignWare UFS Host Controller Joao Pinto
2016-01-07 9:44 ` Christoph Hellwig
2016-01-08 14:20 ` Akinobu Mita
2016-01-08 15:51 ` Joao Pinto
2016-01-13 18:41 ` Joao Pinto
2016-01-14 2:54 ` Akinobu Mita
2016-01-14 9:58 ` Joao Pinto
2016-01-27 17:04 ` Joao Pinto
2016-01-28 12:35 ` Akinobu Mita
2016-01-28 17:00 ` Joao Pinto [this message]
2016-01-28 18:07 ` Joao Pinto
2016-01-28 18:21 ` Joao Pinto
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=56AA492C.80707@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=akinobu.mita@gmail.com \
--cc=gbroner@codeaurora.org \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=subhashj@codeaurora.org \
--cc=ygardi@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).