Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752988AbdFVMiH (ORCPT ); Thu, 22 Jun 2017 08:38:07 -0400 Received: from szxga02-in.huawei.com ([45.249.212.188]:8816 "EHLO szxga02-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751177AbdFVMiD (ORCPT ); Thu, 22 Jun 2017 08:38:03 -0400 Subject: Re: [PATCH v2 2/5] dt-bindings: scsi: ufs: add document for hi3660-ufs To: Arnd Bergmann References: <20170616065119.10704-1-butao@hisilicon.com> <20170616065119.10704-3-butao@hisilicon.com> <0f79aeea-53e3-6bea-ffa6-0e057f2ff83b@huawei.com> <24438c4d-21c8-6302-acd4-4f0e223232ce@huawei.com> CC: Rob Herring , Mark Rutland , "Wei Xu" , Catalin Marinas , "Will Deacon" , Vinayak Holikatti , "James E.J. Bottomley" , "Martin K. Petersen" , Kevin Hilman , "Gregory CLEMENT" , Thomas Petazzoni , Masahiro Yamada , Riku Voipio , Thierry Reding , Krzysztof Kozlowski , Eric Anholt , , "Linux Kernel Mailing List" , Linux ARM , , "Guodong Xu" , , From: Bu Tao Message-ID: Date: Thu, 22 Jun 2017 20:23:33 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.142.51.208] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0202.594BB6E6.0069,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2014-11-16 11:51:01, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 1f99031b066954e34c611c7a0a653a6d Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1665 Lines: 50 在 2017/6/22 20:15, Arnd Bergmann 写道: > On Thu, Jun 22, 2017 at 1:58 PM, Bu Tao wrote: >> 在 2017/6/22 19:51, Arnd Bergmann 写道: >>> On Thu, Jun 22, 2017 at 1:44 PM, Bu Tao wrote: >>>> 在 2017/6/17 5:51, Arnd Bergmann 写道: >>>>> On Fri, Jun 16, 2017 at 8:51 AM, Bu Tao 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.