devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bu Tao <butao@huawei.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>, Eric Anholt <eric@anholt.net>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Vinayak Holikatti <vinholikatti@gmail.com>,
	"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
	linux-scsi@vger.kernel.org, Kevin Hilman <khilman@baylibre.com>,
	Wei Xu <xuwei5@hisilicon.com>,
	Thierry Reding <treding@nvidia.com>,
	devicetree@vger.kernel.org, suzhuangluan@hisilicon.com,
	kongfei@hisilicon.com, Rob Herring <robh+dt@kernel.org>,
	Gregory CLEMENT <gregory.clement@free-electrons.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Guodong Xu <guodong.xu@linaro.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Riku Voipio <riku.voipio@linaro.org>Linux
Subject: Re: [PATCH v2 2/5] dt-bindings: scsi: ufs: add document for hi3660-ufs
Date: Thu, 22 Jun 2017 20:23:33 +0800	[thread overview]
Message-ID: <f63c5e13-74d2-280c-af80-22ee55d71282@huawei.com> (raw)
In-Reply-To: <CAK8P3a1MRx5zRp5-7iDY32+6PGsyHFaOom-bkWmftpLUS=8gBA@mail.gmail.com>



在 2017/6/22 20:15, Arnd Bergmann 写道:
> On Thu, Jun 22, 2017 at 1:58 PM, Bu Tao <butao@huawei.com> wrote:
>> 在 2017/6/22 19:51, Arnd Bergmann 写道:
>>> On Thu, Jun 22, 2017 at 1:44 PM, Bu Tao <butao@huawei.com> wrote:
>>>> 在 2017/6/17 5:51, Arnd Bergmann 写道:
>>>>> On Fri, Jun 16, 2017 at 8:51 AM, Bu Tao <butao@hisilicon.com> wrote:
>>>>
>>>> I do not know wheher other SoC need to use the optional properties as
>>>> abover. So here the name of the optional properties has "hi3660".
>>>
>>>
>>> They should not have "hi3660" in their names either way, independent
>>> of where they are used.
>>
>>
>> Oh, change the "hi3660" to "hisilicon"?
>> e.g. ufs-hi3660-use-rate-B  -->  ufs-hisilicon-use-rate-B
>
> No, just 'use-rate-B', no prefix for this.
>
>>>>> (note: this is different from the value of the "compatible" property
>>>>> that
>>>>> is meant to be as specific as possible".
>>>>>
>>>>> Also, please clarify how your binding relates to the ufshcd binding
>>>>> in Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt: does
>>>>> hi3660 implement any registers that are shared with ufshcd, or does
>>>>> it use the same physical interface with a different register set?
>>>>
>>>>
>>>> No, only show how to use the dt-binding for hi3660 SoC
>>>
>>>
>>> My question was about the hardware: does hi3660 implement ufshcd
>>> or not?
>>
>>
>> YES
>
> Ok, then the properties should be documented as optional in the
> Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt file for anything
> that has a proper interpretation in the context of the generic ufshcd
> driver.
>
>       Arnd
>

OK I will modify this and update the patch soon.


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2017-06-22 12:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16  6:51 [PATCH v2 0/5] scsi: ufs: add ufs driver code for Hi3660 SoC Bu Tao
2017-06-16  6:51 ` [PATCH v2 1/5] scsi: ufs: add hi3660 ufs driver code Bu Tao
2017-06-16  6:51 ` [PATCH v2 2/5] dt-bindings: scsi: ufs: add document for hi3660-ufs Bu Tao
     [not found]   ` <20170616065119.10704-3-butao-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2017-06-16 21:51     ` Arnd Bergmann
2017-06-22 11:44       ` Bu Tao
2017-06-22 11:51         ` Arnd Bergmann
2017-06-22 11:58           ` Bu Tao
     [not found]             ` <24438c4d-21c8-6302-acd4-4f0e223232ce-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-06-22 12:15               ` Arnd Bergmann
2017-06-22 12:23                 ` Bu Tao [this message]
     [not found]           ` <CAK8P3a2z7VbPb95Ltj=Duh1v_Yqxedb_g=ADNPWOrpEz1dCTuw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-23  1:05             ` Subhash Jadavani
2017-06-23  1:09               ` Bu Tao
     [not found] ` <20170616065119.10704-1-butao-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2017-06-16  6:51   ` [PATCH v2 3/5] arm64: dts: Add ufs dts node Bu Tao
2017-06-18  0:31     ` kbuild test robot
     [not found]       ` <201706180814.Kte2462z%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-06-18  7:06         ` Guodong Xu
2017-06-16  6:51 ` [PATCH v2 4/5] arm64: defconfig: enable configs for hi3660 ufs Bu Tao
2017-06-16  6:51 ` [PATCH v2 5/5] arm64: defconfig: enable f2fs and squashfs Bu Tao

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=f63c5e13-74d2-280c-af80-22ee55d71282@huawei.com \
    --to=butao@huawei.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=eric@anholt.net \
    --cc=gregory.clement@free-electrons.com \
    --cc=guodong.xu@linaro.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=khilman@baylibre.com \
    --cc=kongfei@hisilicon.com \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=martin.petersen@oracle.com \
    --cc=riku.voipio@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=suzhuangluan@hisilicon.com \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=treding@nvidia.com \
    --cc=vinholikatti@gmail.com \
    --cc=will.deacon@arm.com \
    --cc=xuwei5@hisilicon.com \
    --cc=yamada.masahiro@socionext.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).