Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp2131682imd; Fri, 2 Nov 2018 06:32:30 -0700 (PDT) X-Google-Smtp-Source: AJdET5fY5Lzw9lj/gv9DRfiUnkA6kvnC5sgaIue8lGM6edCVFiitLAmR8XRpoXTl+uGicKuj9ShE X-Received: by 2002:a17:902:930a:: with SMTP id bc10-v6mr12073332plb.17.1541165550266; Fri, 02 Nov 2018 06:32:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1541165550; cv=none; d=google.com; s=arc-20160816; b=cMM2nfKoaBW7Zd4sW7jba9WbJzDjLcF1U+kP1KkyAPeUa0/X+BqAG2NrzjaQtMKL/M YJKeoiLjUk3sl7yDtysY4Xe6SYQ0y6NDeYTV9hEo2ZHTzGiu+TkK24cy37ypGBn5wlw0 tqlGuFOaacSG6xZ5W5XGymU/IrVXkwRqXQOKmAl17mzQQ7bxjuUXGnyqSY5xX+C4OuzZ K/QIAAXWJoxYCPnD5zRV1X31PtMOMjZav7LPh5eLPJfDRqdpyjXohZgu2psrzTYdfVjx VufPvT/lSZj/f0ABXOhKawM/N7U/WZtaU6ZcYfwEV3Ku0ctft3YsyR2InrgT3o5ooQ+I 8wvw== 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=pmo7MxSbHAq0gJunhRfLdHu5UHKb2jfxj7ngXetIXLo=; b=ugKd8k0M6/bqxth5XA4ELqL8nxSeWtSHFUNYAo/3HywfcRQZ5Y63AhiU1AnR3wJ3fF QHe7XLjiOPhDO0onPIpys8uRw+iap+i+5JFCW6chGRfbwz1aYfOEPHzGXo6CXOmGwHTf WW3Fv8AhumspSt2R+ryJS6cFMEAg/BsnTUsfxJRGZxEk267lTVDOFRG/Hwe5DJrkxBdB B/pYQ+CU5Bnn6FLQWy6NlIog59Mrx67F+ACFCwlRWUSPGPQ+KYwNYRyqXr5rLoqvbKB8 0qkjbopFkjl2TT/asezVr8aN08m2tzJ9ejHCpfotXqdnsyDJBo9ZeD46oTrbEWSHoVWt 5QHw== 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 q85-v6si34866861pfi.183.2018.11.02.06.32.13; Fri, 02 Nov 2018 06:32:30 -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 S1727709AbeKBWiT (ORCPT + 99 others); Fri, 2 Nov 2018 18:38:19 -0400 Received: from foss.arm.com ([217.140.101.70]:41716 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726026AbeKBWiT (ORCPT ); Fri, 2 Nov 2018 18:38:19 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 7AEDCA78; Fri, 2 Nov 2018 06:31:09 -0700 (PDT) Received: from e107155-lin (e107155-lin.cambridge.arm.com [10.1.196.42]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 2E8743F71D; Fri, 2 Nov 2018 06:31:07 -0700 (PDT) Date: Fri, 2 Nov 2018 13:31:00 +0000 From: Sudeep Holla To: Rob Herring Cc: Atish Patra , linux-riscv@lists.infradead.org, Palmer Dabbelt , Anup Patel , Christoph Hellwig , Damien.LeMoal@wdc.com, Thomas Gleixner , Mark Rutland , "linux-kernel@vger.kernel.org" , devicetree@vger.kernel.org, alankao@andestech.com, Zong Li Subject: Re: [RFC 1/2] dt-bindings: topology: Add RISC-V cpu topology. Message-ID: <20181102133100.GA13130@e107155-lin> References: <1541113468-22097-1-git-send-email-atish.patra@wdc.com> <1541113468-22097-2-git-send-email-atish.patra@wdc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 02, 2018 at 08:09:39AM -0500, Rob Herring wrote: > On Thu, Nov 1, 2018 at 6:04 PM Atish Patra wrote: > > > > Define a RISC-V cpu topology. This is based on cpu-map in ARM world. > > But it doesn't need a separate thread node for defining SMT systems. > > Multiple cpu phandle properties can be parsed to identify the sibling > > hardware threads. Moreover, we do not have cluster concept in RISC-V. > > So package is a better word choice than cluster for RISC-V. > > There was a proposal to add package info for ARM recently. Not sure > what happened to that, but we don't need 2 different ways. > We still need that, I can brush it up and post what Lorenzo had previously proposed[1]. We want to keep both DT and ACPI CPU topology story aligned. -- Regards, Sudeep [1] https://marc.info/?l=devicetree&m=151817774202854&w=2