From: Ingo Molnar <mingo@elte.hu>
To: "Pan, Jacob jun" <jacob.jun.pan@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@linux.intel.com>
Subject: Re: [PATCH 3/9] x86/moorestown: add moorestown platform flags
Date: Fri, 26 Jun 2009 09:19:55 +0200 [thread overview]
Message-ID: <20090626071955.GG14078@elte.hu> (raw)
In-Reply-To: <43F901BD926A4E43B106BF17856F07556412B7E2@orsmsx508.amr.corp.intel.com>
* Pan, Jacob jun <jacob.jun.pan@intel.com> wrote:
> >From 365e3a59c34055490f137af2da281d4305535237 Mon Sep 17 00:00:00 2001
> From: Jacob Pan <jacob.jun.pan@intel.com>
> Date: Thu, 11 Jun 2009 09:42:42 -0700
> Subject: [PATCH] x86/moorestown: add moorestown platform flags
>
> This patch adds some new features to the x86 platform feature flags.
>
> These new features are first introduced in Intel Moorestown platform but
> may continue to be present in the next generations.
>
> Feature flags are initialized based on HW subarchitecture ID provided
> by the FW via boot protocol.
>
> Signed-off-by: Jacob Pan <jacob.jun.pan@intel.com>
> ---
> arch/x86/Kconfig | 13 ++++++++++++-
> arch/x86/include/asm/platform_feature.h | 2 ++
> arch/x86/kernel/platform_info.c | 12 +++++++++++-
> 3 files changed, 25 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index d1430ef..c48c291 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -1658,7 +1658,18 @@ config CMDLINE_OVERRIDE
>
> This is used to work around broken boot loaders. This should
> be set to 'N' under normal conditions.
> -
> +config MRST
> + bool "Moorestown MID platform"
> + default n
> + depends on X86_32
> + select SFI
> + help
> + Moorestown is Intel's Low Power Intel Architecture (LPIA) based Moblin
> + Internet Device(MID) platform. Moorestown consists of two chips:
> + Lincroft (CPU core, graphics, and memory controller) and Langwell IOH.
> + Unlike standard x86 PCs, Moorestown does not have many legacy devices
> + nor standard legacy replacement devices/features. e.g. Moorestown does
> + not contain i8259, i8254, HPET, legacy BIOS, most of the io ports.
> endmenu
>
> config ARCH_ENABLE_MEMORY_HOTPLUG
> diff --git a/arch/x86/include/asm/platform_feature.h b/arch/x86/include/asm/platform_feature.h
> index bcadda5..026bdc7 100644
> --- a/arch/x86/include/asm/platform_feature.h
> +++ b/arch/x86/include/asm/platform_feature.h
> @@ -45,6 +45,8 @@
> #define X86_PLATFORM_FEATURE_ACPI (0*32+8) /* has ACPI support */
> #define X86_PLATFORM_FEATURE_SFI (0*32+9) /* has SFI support */
> #define X86_PLATFORM_FEATURE_8042 (0*32+10) /* i8042 KBC */
> +#define X86_PLATFORM_FEATURE_APBT (0*32+11) /* APB timer */
> +#define X86_PLATFORM_FEATURE_VRTC (0*32+12) /* virtual RTC */
>
> extern __u32 platform_feature[N_PLATFORM_CAPINTS];
> extern const char *const
> diff --git a/arch/x86/kernel/platform_info.c b/arch/x86/kernel/platform_info.c
> index b39898a..3021ea9 100644
> --- a/arch/x86/kernel/platform_info.c
> +++ b/arch/x86/kernel/platform_info.c
> @@ -105,7 +105,17 @@ static int __init sysfs_platforminfo_init(void)
> }
> arch_initcall(sysfs_platforminfo_init);
>
> +/* Initialize a set of default feature flags based on subarch IDs
> + * Currently, only MRST platform has non-X86 PC standard feature set.
> + */
please use the customary comment style:
/*
* Comment .....
* ...... goes here:
*/
specified in Documentation/CodingStyle.
> void platform_feature_init_default(int subarch_id)
> {
> - printk(KERN_INFO "Use default X86 platform feature set\n");
> + if ((subarch_id >= 0) && (subarch_id < N_X86_SUBARCHS)) {
> + if (subarch_id == X86_SUBARCH_MRST) {
> + setup_mrst_default_feature();
> + return;
> + }
> + } else {
> + printk(KERN_INFO "Use default X86 platform feature set\n");
> + }
> }
Why dont we have some clean and robust PCI config space based
enumeration instead of this boot ID based thing?
Ingo
next prev parent reply other threads:[~2009-06-26 7:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 0:14 [PATCH 3/9] x86/moorestown: add moorestown platform flags Pan, Jacob jun
2009-06-26 7:19 ` Ingo Molnar [this message]
2009-06-26 9:13 ` Alan Cox
2009-06-26 9:38 ` Ingo Molnar
2009-06-26 10:16 ` Alan Cox
2009-06-26 11:04 ` Ingo Molnar
2009-06-26 11:56 ` Alan Cox
2009-06-26 12:22 ` Ingo Molnar
2009-06-26 12:33 ` Alan Cox
2009-06-26 12:51 ` Ingo Molnar
2009-06-26 13:34 ` Alan Cox
2009-06-26 14:44 ` Ingo Molnar
2009-06-26 14:29 ` Ingo Molnar
2009-06-26 16:32 ` Thomas Gleixner
2009-06-26 16:54 ` Jesse Barnes
2009-06-30 6:35 ` Pavel Machek
2009-07-01 17:25 ` Jesse Barnes
2009-07-01 20:48 ` Ingo Molnar
2009-06-26 15:00 ` Ingo Molnar
2009-06-26 16:51 ` Jesse Barnes
2009-06-26 18:45 ` Ingo Molnar
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=20090626071955.GG14078@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@linux.intel.com \
--cc=jacob.jun.pan@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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.