From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 3/3] x86: Intel MID platforms has no microcode update
Date: Tue, 14 Feb 2017 17:47:14 +0300 [thread overview]
Message-ID: <20170214144714.96516-3-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20170214144714.96516-1-andriy.shevchenko@linux.intel.com>
There is no microcode update available for SoCs used on Intel MID
platforms.
Use conditional to bypass it.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
arch/x86/cpu/mp_init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/cpu/mp_init.c b/arch/x86/cpu/mp_init.c
index 988073cc79..4e2f000f75 100644
--- a/arch/x86/cpu/mp_init.c
+++ b/arch/x86/cpu/mp_init.c
@@ -248,7 +248,7 @@ static int load_sipi_vector(atomic_t **ap_countp, int num_cpus)
if (!stack)
return -ENOMEM;
params->stack_top = (u32)(stack + size);
-#if !defined(CONFIG_QEMU) && !defined(CONFIG_HAVE_FSP)
+#if !defined(CONFIG_QEMU) && !defined(CONFIG_HAVE_FSP) && !defined(CONFIG_INTEL_MID)
params->microcode_ptr = ucode_base;
debug("Microcode at %x\n", params->microcode_ptr);
#endif
--
2.11.0
next prev parent reply other threads:[~2017-02-14 14:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 14:47 [U-Boot] [PATCH v1 1/3] x86: Introduce INTEL_MID quirk option Andy Shevchenko
2017-02-14 14:47 ` [U-Boot] [PATCH v1 2/3] x86: zImage: add Intel MID platforms support Andy Shevchenko
2017-02-15 3:08 ` Bin Meng
2017-02-16 20:44 ` Simon Glass
2017-02-14 14:47 ` Andy Shevchenko [this message]
2017-02-15 3:10 ` [U-Boot] [PATCH v1 3/3] x86: Intel MID platforms has no microcode update Bin Meng
2017-02-15 9:52 ` Andy Shevchenko
2017-02-17 1:22 ` Bin Meng
2017-02-17 13:44 ` Andy Shevchenko
2017-02-16 20:44 ` Simon Glass
2017-02-15 3:00 ` [U-Boot] [PATCH v1 1/3] x86: Introduce INTEL_MID quirk option Bin Meng
2017-02-15 9:50 ` Andy Shevchenko
2017-02-15 10:09 ` Bin Meng
2017-02-15 10:15 ` Andy Shevchenko
2017-02-17 1:19 ` Bin Meng
2017-02-16 20:44 ` Simon Glass
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=20170214144714.96516-3-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox