Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp1013542imd; Thu, 1 Nov 2018 08:58:43 -0700 (PDT) X-Google-Smtp-Source: AJdET5fQIewP78r8KmRYr35M06VaIgZ7gNT3rJchEXRQ64yCGSMFhum7ub8RoZK39XuRIEq9NOSq X-Received: by 2002:a65:610e:: with SMTP id z14-v6mr7673674pgu.138.1541087923306; Thu, 01 Nov 2018 08:58:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1541087923; cv=none; d=google.com; s=arc-20160816; b=mTt1XfkIkWPZ8wRFRUJ7YbXYxlUTLQHVa09b9o66f1RkC6BlEh2rm/vfp/+ZBc9yOb uR9ebPecTN+f4U/tJQwZKAVLw06LehLpgfXOrALfgyFOPcS/nKGXwlGC3FnylaxelFq4 P3GAslIh9dePVPb6t0JVj0pI/yceBDsZGMhkvNWtFFloVQZYbv4tjSWcQd99CLGwXbjN qiS9AcL/jESqAiR5HpbLf+UbK8L9kMDj3y/6EzyvVHgitx4ndOhAIdSpAUsrqEIRgx1P nccIkoToO/zDO0Hb2W9EbYgHjTKe/l1EFFrJzbEXAsuUDCM+NegamkjkWJYtavN2JO0Z lpwA== 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 :in-reply-to:references:mime-version:dkim-signature; bh=dSJCI9kE3qlgUTmBWO4YVagMCHYUBBnirKIyof1dfps=; b=nvUKA+Ov5mxFhp11numg+dY31zdzIjmpBEAL98ZL7k4IPEp9EOFUfcNVK8jbXRfbWP VwG0bHLErHPrG6SoKlWPsRb2KrrEFNEgShJFFpQ9hmFG+iaJ6lM/ylk1wt7Rk7pYLKE2 HRDOZnGp66BxjV27qIx6HaYsDYhUQD0os/oxXC5rlOZA2bUNey47Fot5pDfrAahoXpYR FH5qXK+THcxclxsjuv+vhc63yn6tfQsRD8SsmtrFHev1PkPd3wKK8/iJa78YSg634Egp 0Gl6it6mU60s95ONeM58BXMZ+skDHC3UAjWUTIWXsP2NtIfjF50bANorEr/okjrfPGrG FD9Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=laTLb0pa; 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 134-v6si31164921pfu.273.2018.11.01.08.58.28; Thu, 01 Nov 2018 08:58:43 -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; dkim=pass header.i=@kernel.org header.s=default header.b=laTLb0pa; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729122AbeKBBBT (ORCPT + 99 others); Thu, 1 Nov 2018 21:01:19 -0400 Received: from mail.kernel.org ([198.145.29.99]:58880 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728665AbeKBBBS (ORCPT ); Thu, 1 Nov 2018 21:01:18 -0400 Received: from mail-qt1-f175.google.com (mail-qt1-f175.google.com [209.85.160.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 8B2CC2082E; Thu, 1 Nov 2018 15:57:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1541087864; bh=dSJCI9kE3qlgUTmBWO4YVagMCHYUBBnirKIyof1dfps=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=laTLb0paqRoDWv5D7uguyobFglasgGw8oHoQKLvFJcAwOetkPNpKMWDD0SmKO+fRk szyBKDeK+5p8BzbeVfCrZeyV0jBqxj/YVRT5UKZVYrRFSrtQDTCd6EwiOKpWeV+lo5 kSmrM0H/nKVp6siKQbAZyVB5Rj8G6xhwrsFKQlc4= Received: by mail-qt1-f175.google.com with SMTP id v1-v6so17394193qtq.5; Thu, 01 Nov 2018 08:57:44 -0700 (PDT) X-Gm-Message-State: AGRZ1gJSS4kNrwSYCvDI9RARBKwYXYx65wmIf5YWemPpst512BdRM7rv JgmdAyzvdjASK8P5kTf1YdcP+jk9nZK06dAOjA== X-Received: by 2002:ac8:6b18:: with SMTP id w24mr7435448qts.144.1541087863786; Thu, 01 Nov 2018 08:57:43 -0700 (PDT) MIME-Version: 1.0 References: <20180905193738.19325-1-robh@kernel.org> <20180905193738.19325-2-robh@kernel.org> <874ld3jz6v.fsf@concordia.ellerman.id.au> <871s87jz3g.fsf@concordia.ellerman.id.au> <87tvl1dq7q.fsf@concordia.ellerman.id.au> <20181101151201.GJ5994@gate.crashing.org> In-Reply-To: <20181101151201.GJ5994@gate.crashing.org> From: Rob Herring Date: Thu, 1 Nov 2018 10:57:31 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 01/21] of: Add cpu node iterator for_each_of_cpu_node() To: segher@kernel.crashing.org Cc: Michael Ellerman , devicetree@vger.kernel.org, linuxppc-dev , "linux-kernel@vger.kernel.org" , Frank Rowand , Tyrel Datwyler 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 On Thu, Nov 1, 2018 at 10:12 AM Segher Boessenkool wrote: > > On Thu, Nov 01, 2018 at 09:52:57PM +1100, Michael Ellerman wrote: > > Rob Herring writes: > > > Yes, I was aware at least older powerpc DTs don't use 'cpu' for node names. > > > > Actually newer ones too, see below :) > > Good, because that is required by the Open Firmware standard (the PowerPC > binding, to be exact): > > http://www.openbios.org/data/docs/ppc-2_1.ps > > (see 5.1.4, "name"). Yes. I should say I only expect systems following ePAPR (3.7) or DT Spec will use 'cpu' node names. Those specs also require 'device_type' which is supposed to indicate what OF methods are available for a node which doesn't exist on FDT. Rob