LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Ivan Gorinov <ivan.gorinov@intel.com>
Cc: Frank Rowand <frowand.list@gmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v6 1/2] of: Documentation: Specify local APIC ID in "reg"
Date: Mon, 19 Mar 2018 14:06:06 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1803191405340.2010@nanos.tec.linutronix.de> (raw)
In-Reply-To: <c5eb2fd010855d187007859e7a332c866fbd41ec.1520974793.git.ivan.gorinov@intel.com>
Rob,
On Tue, 13 Mar 2018, Ivan Gorinov wrote:
> Use the "reg" property to specify the processor's local APIC ID.
> Local APIC ID is assigned by hardware and may differ from CPU number.
Any opinion on this version?
Thanks,
tglx
> Signed-off-by: Ivan Gorinov <ivan.gorinov@intel.com>
> ---
> 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..1c41cbd 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
>
>
next prev parent reply other threads:[~2018-03-19 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 22:04 [PATCH v6 0/2] x86/devicetree: Enable multiprocessing Ivan Gorinov
2018-03-13 22:05 ` [PATCH v6 1/2] of: Documentation: Specify local APIC ID in "reg" Ivan Gorinov
2018-03-19 13:06 ` Thomas Gleixner [this message]
2018-03-20 0:39 ` Rob Herring
2018-03-20 18:10 ` Ivan Gorinov
2018-03-20 18:26 ` Thomas Gleixner
2018-03-13 22:05 ` [PATCH v6 2/2] x86/devicetree: Use CPU description from Device Tree Ivan Gorinov
2018-03-19 22:29 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1803191405340.2010@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=andy.shevchenko@gmail.com \
--cc=frowand.list@gmail.com \
--cc=ivan.gorinov@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=robh+dt@kernel.org \
--subject='Re: [PATCH v6 1/2] of: Documentation: Specify local APIC ID in "reg"' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).