Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp650394imm; Fri, 28 Sep 2018 04:43:04 -0700 (PDT) X-Google-Smtp-Source: ACcGV60eOLRKNekFvdF/xSi79riHF2N2zYaGG+RLsNs2narFzm3BqDvnJuCH8RKWLdk6vSN/e1vY X-Received: by 2002:a62:5543:: with SMTP id j64-v6mr16180739pfb.188.1538134984074; Fri, 28 Sep 2018 04:43:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538134984; cv=none; d=google.com; s=arc-20160816; b=IbsvhTZyzoI/NQI7Wu6EOZa7jxE5kOHGFtW0uH11KyH746imdhAYFK9Ls+P3wI2FMD KPfMVOCSSJ9Rm05aeqmNh0BiXD32vhAGTaQnitW9hoEbMsGbnkJGkoLy1CyE6h65eUkI zqkyjIt8Fnf+eWBRswTWALmTNr+N2sXWwvcgswZ+sS+rhSUR5YQ8+vCqblxRwmDcUTkV a4jDVliWOkaYPa9wMi9I7Gw3YYZwSJmzqqklKgThn3CaqmYUZEU50vEfaMBhiBMVViol e7lI8VSV31GqKQ15aweIH6ZS3273rFunA6zE9kh9m1XzyzhQ7fY5MvY0ezE5iUL6oQkC eaDQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=06XLbjrGE8t7K9jy0r6DtWBjnhLjACbvZwwYlidSmGg=; b=G87ODL/gcxATEu0hyU5KF3TR4m7BdDoGQ2OlkPWazO4HsZ4XtYVgiPJ2sZOa3cpjV8 skgn+QdbCKyYq/VwNVN4rg7BHzgcANHWqLdbTevn3Qy3lg+uxPXTJyVAZ59AmeIGMfgT t2xTHQZOdrEgt/1OmmZ0n2F8T7zhkS2BVbsZWVxIvfNAjHF93fs8yxrRCetuqGvkOBsD ArIXa7A8ll+SzKqnfTIwSSbIvkSJve2Lx2j4emcwJQusSuD6rrOTQDkqYUlXVua5z72E ytcgKtVmfXzYLkbS0+Y5FMyPiWPTsFQvqs0+CuUGEiQKyy2Vo2/S1Bv16VvrO/TOP17N J/Jg== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c2-v6si4469548pgm.236.2018.09.28.04.42.47; Fri, 28 Sep 2018 04:43:04 -0700 (PDT) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729635AbeI1SGF (ORCPT + 99 others); Fri, 28 Sep 2018 14:06:05 -0400 Received: from smtp2200-217.mail.aliyun.com ([121.197.200.217]:40968 "EHLO smtp2200-217.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729257AbeI1SGE (ORCPT ); Fri, 28 Sep 2018 14:06:04 -0400 X-Alimail-AntiSpam: AC=CONTINUE;BC=0.07458846|-1;CH=green;FP=0|0|0|0|0|-1|-1|-1;HT=e02c03303;MF=ren_guo@c-sky.com;NM=1;PH=DS;RN=17;RT=17;SR=0;TI=SMTPD_---.Cx--6QH_1538134924; Received: from localhost(mailfrom:ren_guo@c-sky.com fp:SMTPD_---.Cx--6QH_1538134924) by smtp.aliyun-inc.com(10.147.41.138); Fri, 28 Sep 2018 19:42:05 +0800 Date: Fri, 28 Sep 2018 19:42:04 +0800 From: Guo Ren To: Rob Herring Cc: Andrew Morton , Arnd Bergmann , Daniel Lezcano , David Miller , Greg Kroah-Hartman , Jason Cooper , Marc Zyngier , Mark Rutland , Mauro Carvalho Chehab , Peter Zijlstra , Thomas Gleixner , "linux-kernel@vger.kernel.org" , "open list:GENERIC INCLUDE/ASM HEADER FILES" , devicetree@vger.kernel.org, Greentime Hu , Palmer Dabbelt Subject: Re: [PATCH V5 18/30] dt-bindings: csky CPU Bindings Message-ID: <20180928114204.GA335@guoren-Inspiron-7460> References: <62098e7d0a7fbdd09f44d7e23333dad258a01bd2.1537789737.git.ren_guo@c-sky.com> <20180927164317.GA8427@bogus> <20180928010312.GA4179@guoren-Inspiron-7460> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 28, 2018 at 06:32:34AM -0500, Rob Herring wrote: > On Thu, Sep 27, 2018 at 8:03 PM Guo Ren wrote: > > > > On Thu, Sep 27, 2018 at 11:43:17AM -0500, Rob Herring wrote: > > > On Tue, Sep 25, 2018 at 07:39:21AM +0800, Guo Ren wrote: > > > > This patch adds the documentation to describe that how to add cpu nodes in > > > > dts for SMP. > > > > > > > > Signed-off-by: Guo Ren > > > > --- > > > > Documentation/devicetree/bindings/csky/cpus.txt | 70 +++++++++++++++++++++++++ > > > > 1 file changed, 70 insertions(+) > > > > create mode 100644 Documentation/devicetree/bindings/csky/cpus.txt > > > > > > > > diff --git a/Documentation/devicetree/bindings/csky/cpus.txt b/Documentation/devicetree/bindings/csky/cpus.txt > > > > new file mode 100644 > > > > index 0000000..ee3901d > > > > --- /dev/null > > > > +++ b/Documentation/devicetree/bindings/csky/cpus.txt > > > > @@ -0,0 +1,70 @@ > > > > +================== > > > > +C-SKY CPU Bindings > > > > +================== > > > > + > > > > +The device tree allows to describe the layout of CPUs in a system through > > > > +the "cpus" node, which in turn contains a number of subnodes (ie "cpu") > > > > +defining properties for every cpu. > > > > + > > > > +Only SMP system need to care about the cpus node and single processor > > > > +needn't define cpus node at all. > > > > > > We've generally found this is not true. Even for single core, you can > > > have power domains, clocks for DVFS, etc. > > Ok, I'll remove it. > > > > > > > > > + > > > > +===================================== > > > > +cpus and cpu node bindings definition > > > > +===================================== > > > > + > > > > +- cpus node > > > > + > > > > + Description: Container of cpu nodes > > > > + > > > > + The node name must be "cpus". > > > > + > > > > + A cpus node must define the following properties: > > > > + > > > > + - #address-cells > > > > + Usage: required > > > > + Value type: > > > > + Definition: must be set to 1 > > > > + - #size-cells > > > > + Usage: required > > > > + Value type: > > > > + Definition: must be set to 0 > > > > + > > > > +- cpu node > > > > + > > > > + Description: Describes one of SMP cores > > > > + > > > > + PROPERTIES > > > > + > > > > > > You need a compatible property for cpu nodes. > > Our cpu is defined in defconfig, not in dts. I could put a comatible > > property in here, but it's no use in code. > > It doesn't matter as that could change. Most arches do run-time > selection of cpus within a range of compatible cores. > > And read the DT spec (devicetree.org) which says compatible is > required for cpu nodes. Ok, follow the rules. Here is my design.. - compatible: Usage: required Value type: Definition: csky,: "csky,610" "csky,807" "csky,810" "csky,860" Best Regards Guo Ren