From: Ivan Gorinov <ivan.gorinov@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Frank Rowand <frowand.list@gmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: 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: [PATCH v8 0/2] x86/devicetree: Enable multiprocessing
Date: Thu, 22 Mar 2018 14:35:19 -0700 [thread overview]
Message-ID: <cover.1521753738.git.ivan.gorinov@intel.com> (raw)
Current x86 implementation of Device Tree does not support multiprocessing,
and the bindings documentation describes the "reg" property of "cpu" nodes
as "CPU number" instead of hardware-assigned local APIC ID.
v8:
* Fixed build error with CONFIG_X86_LOCAL_APIC=n reported by kbuild.
v7:
* Change log update.
v6:
* Calling of_property_read_u32() to get Local APIC ID from "reg".
* DT documentation changes: corrected CPU node example and changed
the "reg" property description.
v5:
* Using the "reg" property to specify Local APIC ID.
Ivan Gorinov (2):
of: Documentation: Specify local APIC ID in "reg"
x86/devicetree: Use CPU description from Device Tree
Documentation/devicetree/bindings/x86/ce4100.txt | 37 ++++++++++++++-----
arch/x86/kernel/devicetree.c | 45 +++++++++++++++++-------
2 files changed, 61 insertions(+), 21 deletions(-)
--
2.7.4
next reply other threads:[~2018-03-22 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 21:35 Ivan Gorinov [this message]
2018-03-22 21:35 ` [PATCH v8 1/2] of: Documentation: Specify local APIC ID in "reg" Ivan Gorinov
2018-03-25 23:50 ` Rob Herring
2018-03-26 13:19 ` [tip:x86/platform] of/Documentation: " tip-bot for Ivan Gorinov
2018-03-22 21:35 ` [PATCH v8 2/2] x86/devicetree: Use CPU description from Device Tree Ivan Gorinov
2018-03-26 13:19 ` [tip:x86/platform] " tip-bot for Ivan Gorinov
2018-03-23 16:26 ` [PATCH v8 0/2] x86/devicetree: Enable multiprocessing Andy Shevchenko
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=cover.1521753738.git.ivan.gorinov@intel.com \
--to=ivan.gorinov@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.