Received: by 10.223.176.46 with SMTP id f43csp2703450wra; Mon, 22 Jan 2018 01:56:40 -0800 (PST) X-Google-Smtp-Source: AH8x227JvuWrn9o0jS73+R5pQZ/0Wj/Z1IdMW5Y8GnpNQTTy8A3Zi6j180EDNuAfm/pMNxW7WtGZ X-Received: by 2002:a17:902:6716:: with SMTP id f22-v6mr3220452plk.180.1516615000366; Mon, 22 Jan 2018 01:56:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516615000; cv=none; d=google.com; s=arc-20160816; b=gKZFfI+Zw1ZSf4Q0kQoaZKEeOnjvaR3JyNmggNAyBtNfLkmht4eBSF2l3kcBY7xGJu W8pn2HsXLheeB/lqVKvMuXEqFWsxEZ5Fx8+uoAoMXGX/vhAZS7L9GZFDWbMZE2AbBzNs Sm7SRx/NDJuc1axH0Eq6LALlkTzvuMHgs3z7mIoIGROvjtJcdbgmE8h3A9mk92S/OcbC cuIv4HacG1MvkTP65Z+MhkvgbgRjooOKs0PzGcSyLkcjTtLVoFnpWj7S4pCt0Eb+HQIF VOmitP6GJv/v03BafrSL5uPnrD892g3aN5x2NbvKFRIT0143Zuwg0hPo65PEFTydh6vh cuSA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=ycJj24IkPWuINZeY3lKgbD14OFyRHGfs+AMpCcVkx0g=; b=r9mRby/kykiTM26wtabmkAoBR2XtXpdmmm0viQA8fFAN+bCkSutR0Fi84WjPgnieSu p5NsW9LzvNv2swpUsc0PvXW40DfxGGaJu+YW1z9iXefpLmJ2QYQ2kMAwFi/ZOBh3tQog KKRdOgVa/tnqZCpo4BXKlBL+DnMz9uK2Jw01kqCz8KNolBuj704DSICmJ8X1LnnYOF5z /So0sk7/UUZMXGnFZ2JdaJ3mDKznqwKEeXZH8QmszStq4z2mUuOtLUjMt9sxJzrd/ToR 6aAFLnGu5L9gdp2NgCqKLu/3gHTNiOVT2u4GxUjbt735HK4fvI6nYtz2zVGivtB1+mNd 3/6g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=CR8LyfqJ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u185si572261pgd.397.2018.01.22.01.56.26; Mon, 22 Jan 2018 01:56:40 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=CR8LyfqJ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750997AbeAVJyc (ORCPT + 99 others); Mon, 22 Jan 2018 04:54:32 -0500 Received: from mail-ua0-f196.google.com ([209.85.217.196]:39946 "EHLO mail-ua0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751101AbeAVJy3 (ORCPT ); Mon, 22 Jan 2018 04:54:29 -0500 Received: by mail-ua0-f196.google.com with SMTP id t6so5398967ual.7; Mon, 22 Jan 2018 01:54:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ycJj24IkPWuINZeY3lKgbD14OFyRHGfs+AMpCcVkx0g=; b=CR8LyfqJ/W71C2K/xhRKntOnYkGyFxv/vBcO1EjNMkwjLQ/x/HC4cjtIMAJkP7IW23 dX7SL4vPnDpk2O+tS1TzUnOfKh6R+hYZd2atWRdGO6KNsOVkbCWiEi4ujyxXbweLw3W9 KHJhe0eMIbocwYilr0ctzgVbze2aEPH9IJPZAxtMpJT+nHDkDVc1FDRAXofVqnJO/Rug kHT3r+PFPh4IZ5OyDvOXWU4DGrZtG30AeiRyWP0dKMjGafw45leWfqZtGmARa83wjROg Jw3SSfNuhb2DFpQ5Nct6kqLnMwSdV91Mg1HuT274tI/LQ+JS+Q0nJ64dPm1uZiM8/wlE WSlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ycJj24IkPWuINZeY3lKgbD14OFyRHGfs+AMpCcVkx0g=; b=p/HoWB0JEhlfkFXYruU2bI6RI9W6QjH2Y7ptuDnOyDakgt6fV1ZXUWUaVxTYvR+IlE zlfsvty7fCjXJuHpW9cjeMYNdjwD1Ix+2ckKdVsgcQdkUxwhVJUPFIY5A5ayKZJhjJOn k4BKiVic0ALbF5z5y1KMgI9b24Lmh5Za6dWX5ky2Jj0jPbM4V7lzqKxmYKa0l4vpl4vU GHvqk4CgL83roT4MUDRIEhAb56Ls65NKAs9aoBNcz37BaaW/ZKceannUZtUCmmL2oRfi JbKQk2uItZ1vIxzkdyr4TXa8D6T+rbIlui01/tXvOoqY/xoEzrDItKQeLoWrV+pTJbMU lNqg== X-Gm-Message-State: AKwxytdPR+bJtvpFCVN6v4X1VJJ1rKujRxImnRbY1cqCPsPTf0CrtN9A +NhhEYf44VYFMWTjvaJ/b8zKj9e1uIwsgx50JDs= X-Received: by 10.159.57.111 with SMTP id i47mr5341269uag.79.1516614868221; Mon, 22 Jan 2018 01:54:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.159.42.194 with HTTP; Mon, 22 Jan 2018 01:53:47 -0800 (PST) In-Reply-To: References: From: Greentime Hu Date: Mon, 22 Jan 2018 17:53:47 +0800 Message-ID: Subject: Re: [PATCH v6 31/36] dt-bindings: nds32 CPU Bindings To: Geert Uytterhoeven Cc: Arnd Bergmann , Greentime , Linux Kernel Mailing List , linux-arch , Thomas Gleixner , Jason Cooper , Marc Zyngier , Rob Herring , Networking , Vincent Chen , DTML , Al Viro , David Howells , Will Deacon , Daniel Lezcano , linux-serial@vger.kernel.org, Linus Walleij , Mark Rutland , Greg KH , Guo Ren , Randy Dunlap , David Miller , Jonas Bonn , Stefan Kristiansson , Stafford Horne , Vincent Chen , Rick Chen , Zong Li Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Geert: 2018-01-19 23:37 GMT+08:00 Geert Uytterhoeven : > Hi Greentime, > > On Fri, Jan 19, 2018 at 4:35 PM, Greentime Hu wrote: >> 2018-01-19 23:29 GMT+08:00 Geert Uytterhoeven : >>> On Fri, Jan 19, 2018 at 4:18 PM, Greentime Hu wrote: >>>> 2018-01-19 22:52 GMT+08:00 Arnd Bergmann : >>>>> On Fri, Jan 19, 2018 at 3:32 PM, Greentime Hu wrote: >>>>>> 2018-01-18 19:02 GMT+08:00 Arnd Bergmann : >>>>>>> On Mon, Jan 15, 2018 at 6:53 AM, Greentime Hu wrote: >>>>>>>> From: Greentime Hu >>>>>>>> >>>>>>>> This patch adds nds32 CPU binding documents. >>>>>>>> >>>>>>>> Signed-off-by: Vincent Chen >>>>>>>> Signed-off-by: Rick Chen >>>>>>>> Signed-off-by: Zong Li >>>>>>>> Signed-off-by: Greentime Hu >>>>>>>> Reviewed-by: Rob Herring >>>>>>>> --- >>>>>>>> Documentation/devicetree/bindings/nds32/cpus.txt | 37 ++++++++++++++++++++++ >>>>>>>> 1 file changed, 37 insertions(+) >>>>>>>> create mode 100644 Documentation/devicetree/bindings/nds32/cpus.txt >>>>>>>> >>>>>>>> diff --git a/Documentation/devicetree/bindings/nds32/cpus.txt b/Documentation/devicetree/bindings/nds32/cpus.txt >>>>>>>> new file mode 100644 >>>>>>>> index 0000000..9a52937 >>>>>>>> --- /dev/null >>>>>>>> +++ b/Documentation/devicetree/bindings/nds32/cpus.txt >>>>>>>> @@ -0,0 +1,37 @@ >>>>>>>> +* Andestech Processor Binding >>>>>>>> + >>>>>>>> +This binding specifies what properties must be available in the device tree >>>>>>>> +representation of a Andestech Processor Core, which is the root node in the >>>>>>>> +tree. >>>>>>>> + >>>>>>>> +Required properties: >>>>>>>> + >>>>>>>> + - compatible: >>>>>>>> + Usage: required >>>>>>>> + Value type: >>>>>>>> + Definition: should be one of: >>>>>>>> + "andestech,n13" >>>>>>>> + "andestech,n15" >>>>>>>> + "andestech,d15" >>>>>>>> + "andestech,n10" >>>>>>>> + "andestech,d10" >>>>>>>> + "andestech,nds32v3" >>>>>>> >>>>>>> Based on https://lkml.org/lkml/2017/11/27/1290, this should say that >>>>>>> the device tree should always list 'andestech,nds32v3' as the most >>>>>>> generic 'compatible' value and list exactly one of the others in >>>>>>> addition. >>>>> >>>>>> I will remove the others and just left "andestech,nds32v3" in here. >>>>> >>>>> No, is not what we want here, the CPU node should list exactly which core >>>>> is used, what we need in the description is a clarification that >>>>> andestech,nds32v3 must be used in addition to the more specific >>>>> string. >>>> >>>> Hi, Arnd: >>>> >>>> Sorry I still don't get your point. Do you mean we should always use >>>> compatible = "andestech,n13", "andestech,nds32v3"; >>>> instead of >>>> compatible = "andestech,n13"; >>> >>> Exactly. The first value is a device-specific compatible value, the second is >>> a generic fallback. >>> >>>> And I need to add the description in this document. >>> >>> Indeed. See for example >>> Documentation/devicetree/bindings/power/renesas,apmu.txt >>> >>> Thanks! >> >> Hi, Geert: >> >> Thank you and your example. >> I get it. I will update this document like this. >> - compatible: Should be "andestech,", "andestech,nds32v3" >> as fallback. > > And please keep a list of supported values of "andestech," > in the DT binding document, so checkpatch can validate compatible values. > Thank you for reminding me this. I will list it like this. - compatible: Usage: required Value type: Definition: Should be "andestech,", "andestech,nds32v3" as fallback. Examlpes with core_names are: "andestech,n13" "andestech,n15" "andestech,d15" "andestech,n10" "andestech,d10"