Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752929AbdFVMP6 (ORCPT ); Thu, 22 Jun 2017 08:15:58 -0400 Received: from mail-oi0-f68.google.com ([209.85.218.68]:34465 "EHLO mail-oi0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751118AbdFVMP4 (ORCPT ); Thu, 22 Jun 2017 08:15:56 -0400 MIME-Version: 1.0 In-Reply-To: <24438c4d-21c8-6302-acd4-4f0e223232ce@huawei.com> 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> From: Arnd Bergmann Date: Thu, 22 Jun 2017 14:15:54 +0200 X-Google-Sender-Auth: -tPsXlIEC9n7Ugkz9IW2hlzE554 Message-ID: Subject: Re: [PATCH v2 2/5] dt-bindings: scsi: ufs: add document for hi3660-ufs To: Bu Tao 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 , devicetree@vger.kernel.org, Linux Kernel Mailing List , Linux ARM , linux-scsi@vger.kernel.org, Guodong Xu , suzhuangluan@hisilicon.com, kongfei@hisilicon.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id v5MCGB8F022640 Content-Length: 1517 Lines: 44 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