From: Joao Pinto <Joao.Pinto@synopsys.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
Joao Pinto <Joao.Pinto@synopsys.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: UFS patchset
Date: Fri, 29 Apr 2016 13:29:58 +0100 [thread overview]
Message-ID: <572353C6.5070308@synopsys.com> (raw)
In-Reply-To: <yq1h9ekbo9j.fsf@sermon.lab.mkp.net>
On 4/29/2016 1:19 PM, Martin K. Petersen wrote:
>>>>>> "Joao" == Joao Pinto <Joao.Pinto@synopsys.com> writes:
>
> Joao,
>
> Joao> Could you please give me feedback about the UFS patch-set? The
> Joao> patches have been acked by various developers, so maybe could it
> Joao> be possible to put it into the 4.7 queue?
>
> It is on my list.
Ok, great!
>
> I think we are OK from a SCSI perspective but I believe there were still
> a couple of concerns in the ARM/device tree department. So I would like
> some confirmation from those developers that the code is now acceptable.
>
The concerns were from Rob Herring about mixing PHY and controller in the
compatibility string, but that was justified. Check the extract:
">>
>>>
>>> Combining the phy and controller compatible strings is a bit strange.
>>> Generally, they would be separate nodes using the common phy binding.
>>>
>>
>> Correct, but in this case is just the compatibility string is just to
>> tell the dw ufs host that it has a 40-bit or a 20-bit test chip
>> connected. The Test chip is initialized by a unipro command sequence and
there is no more ops related to it.
>
> Okay. In that case, I think it should be a separate property unless
> the controller h/w is synthesized for one or the other.
Yes, the hardware must be synthesized for a certain PHY type, 20 or 40-bit.
>
> Rob
>
Joao"
Thanks,
Joao
next prev parent reply other threads:[~2016-04-29 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 10:24 UFS patchset Joao Pinto
2016-04-29 12:19 ` Martin K. Petersen
2016-04-29 12:29 ` Joao Pinto [this message]
2016-04-30 0:07 ` Martin K. Petersen
2016-04-30 0:24 ` Martin K. Petersen
2016-05-02 9:08 ` Joao Pinto
2016-05-02 13:58 ` 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=572353C6.5070308@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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