LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
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 v6 0/2] x86/devicetree: Enable multiprocessing
Date: Tue, 13 Mar 2018 15:04:50 -0700 [thread overview]
Message-ID: <cover.1520974793.git.ivan.gorinov@intel.com> (raw)
Current x86 implementation of Device Tree does not support multiprocessing,
and the bindings documentation describes the "reg" property as CPU number
instead of hardware-assigned local APIC ID.
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 | 39 +++++++++++++++++-------
2 files changed, 56 insertions(+), 20 deletions(-)
--
2.7.4
next reply other threads:[~2018-03-13 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 22:04 Ivan Gorinov [this message]
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
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=cover.1520974793.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 \
--subject='Re: [PATCH v6 0/2] x86/devicetree: Enable multiprocessing' \
/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).