Received: by 10.213.65.68 with SMTP id h4csp1074113imn; Thu, 22 Mar 2018 14:44:42 -0700 (PDT) X-Google-Smtp-Source: AG47ELvMRpaJMDHtGKfdts896qalrKYBMk9nsB0nBfEFoFHDKSH7jAClRjvGIBJitnL2QdoX/FJy X-Received: by 2002:a17:902:983:: with SMTP id 3-v6mr27235853pln.278.1521755082794; Thu, 22 Mar 2018 14:44:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521755082; cv=none; d=google.com; s=arc-20160816; b=OxQy9ja/cL6/+rTkuZ+jWHiOhJbzTxbzRDYdALQiX6WT3Vb7RPi0i6r8DDdkPleP2Q cySQhQmA8IKlo/Mu9v4wiUhXrQM7LfZUevrHnQvTNmUH6nHVDlhRXVWFBP0yNHO0jDDQ TnhHaXdkJ72WmDRaikagtQzUQywIxiXNl+BnMW2hZtyhy5hjwd+kWwSAIdiWVOIAcCwB Czb0ZvFpIkv5aTCoubGp0Z2KchkuYn15QA3w6QnD/lLCIwU+nAfSEOPYsRlRxXLlIXu4 8mEdba/77nptQo5Zni/1Inxv7XJSXqBuo96Fj0kdPEUJcFHm6beOxA13CL0PhO7rkuKH CGSw== 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:arc-authentication-results; bh=/59WzvdlqLeQjKY9XUSLdQfP2tbwTR4S31bvNM+026c=; b=Rj9nwTizdjCTHpzDwReNIp1/19b3ZsSDhg/Es+Ir31HHY1mL2fmZQiC3K4opj6nztK WQdwrABor855z51YUM0Aq2nLR/F887UigdW/jws2NkK45xtPP7PAy4ZYaipIIWZvFpzm sIWXlZJ4qr/y72t9bVuvcXURc0xMwQvVJ5fLk6VHdqtgIpKZHUq9ycBM18Wxsq278p5y pRre5kQmYsxqAQcJT0Yn5VYFraJCgo6eprR/6oJmrADQ8Ob0lD0SDU5F3odYVpfu9UTp xxGMP/wSWUJ3M4iG+Jb2xCO4Da6apwx1a7ptvNe8+lcRzHSuuuZKhT4s9CP4bkkuO6Z6 KBbg== 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 d25si4143705pge.410.2018.03.22.14.44.28; Thu, 22 Mar 2018 14:44:42 -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 S1751896AbeCVVna (ORCPT + 99 others); Thu, 22 Mar 2018 17:43:30 -0400 Received: from mga05.intel.com ([192.55.52.43]:15755 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751632AbeCVVn2 (ORCPT ); Thu, 22 Mar 2018 17:43:28 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Mar 2018 14:43:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,345,1517904000"; d="scan'208";a="214031802" Received: from dph9ls1.fm.intel.com (HELO intel.com) ([10.80.209.182]) by fmsmga005.fm.intel.com with ESMTP; 22 Mar 2018 14:43:28 -0700 Date: Thu, 22 Mar 2018 14:35:33 -0700 From: Ivan Gorinov To: Thomas Gleixner , Frank Rowand , Andy Shevchenko Cc: Linux Kernel Mailing List , Ingo Molnar , Rob Herring , Mark Rutland Subject: [PATCH v8 1/2] of: Documentation: Specify local APIC ID in "reg" Message-ID: <4b1a471a56ac0ebd7510f4759afce9104595d6da.1521753738.git.ivan.gorinov@intel.com> References: 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 Use the "reg" property to specify the processor's local APIC ID instead of setting it to the CPU node index in Device Tree. Local APIC ID is assigned by hardware and visible in the APIC ID register. Some processor models allow APIC ID to be changed by software, but CPUID instruction executed with %eax = 0x0b always returns the initial ID in %edx. Local APIC ID does not match the node index in many systems. Signed-off-by: Ivan Gorinov --- Documentation/devicetree/bindings/x86/ce4100.txt | 37 ++++++++++++++++++------ 1 file changed, 28 insertions(+), 9 deletions(-) diff --git a/Documentation/devicetree/bindings/x86/ce4100.txt b/Documentation/devicetree/bindings/x86/ce4100.txt index b49ae59..4bbfed1 100644 --- a/Documentation/devicetree/bindings/x86/ce4100.txt +++ b/Documentation/devicetree/bindings/x86/ce4100.txt @@ -7,17 +7,36 @@ Many of the "generic" devices like HPET or IO APIC have the ce4100 name in their compatible property because they first appeared in this SoC. -The CPU node ------------- - cpu@0 { - device_type = "cpu"; - compatible = "intel,ce4100"; - reg = <0>; - lapic = <&lapic0>; +The CPU nodes +------------- + + cpus { + #address-cells = <1>; + #size-cells = <0>; + + cpu@0x00 { + device_type = "cpu"; + compatible = "intel,ce4100"; + reg = <0x00>; + }; + + cpu@0x02 { + device_type = "cpu"; + compatible = "intel,ce4100"; + reg = <0x02>; + }; }; -The reg property describes the CPU number. The lapic property points to -the local APIC timer. +A "cpu" node describes one logical processor (hardware thread). + +Required properties: + +- device_type + Device type, must be "cpu". + +- reg + Local APIC ID, the unique number assigned to each processor by + system hardware. The SoC node ------------ -- 2.7.4