public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: linux acpi <linux-acpi@vger.kernel.org>
Cc: "Brown, Len" <len.brown@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Jarosz, Sebastian" <sebastian.jarosz@intel.com>
Subject: [patch]acpi: add missing _OSI strings -- resend
Date: Mon, 04 Jul 2011 13:23:20 +0800	[thread overview]
Message-ID: <1309757000.15392.221.camel@sli10-conroe> (raw)

Last post (Jun 14 ) is lost, resend.


Linux supports some optional features, but it should notify BIOS about them
in _OSI method. Currently Linux doesn't notify any, which might make such
features not work because BIOS doesn't know about them.

Reported-by: "Jarosz, Sebastian" <sebastian.jarosz@intel.com>
Signed-off-by: Shaohua Li <shaohua.li@intel.com>

diff --git a/drivers/acpi/osl.c b/drivers/acpi/osl.c
index 52ca964..a305115 100644
--- a/drivers/acpi/osl.c
+++ b/drivers/acpi/osl.c
@@ -1083,7 +1083,13 @@ struct osi_setup_entry {
 	bool enable;
 };
 
-static struct osi_setup_entry __initdata osi_setup_entries[OSI_STRING_ENTRIES_MAX];
+static struct osi_setup_entry __initdata
+		osi_setup_entries[OSI_STRING_ENTRIES_MAX] = {
+	{"Module Device", true},
+	{"Processor Device", true},
+	{"3.0 _SCP Extensions", true},
+	{"Processor Aggregator Device", true},
+};
 
 void __init acpi_osi_setup(char *str)
 {



             reply	other threads:[~2011-07-04  5:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-04  5:23 Shaohua Li [this message]
2011-07-04 13:24 ` [patch]acpi: add missing _OSI strings -- resend Matthew Garrett
2011-07-05 22:08 ` Andrew Morton
2011-07-06  0:29   ` Shaohua Li
2011-07-06 12:50     ` Jarosz, Sebastian

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=1309757000.15392.221.camel@sli10-conroe \
    --to=shaohua.li@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=sebastian.jarosz@intel.com \
    /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