From: Len Brown <lenb@kernel.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH] ACPI: Do not modify SCI_EN directly
Date: Tue, 30 Dec 2008 19:03:25 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0812301903210.17126@localhost.localdomain> (raw)
In-Reply-To: <200812291919.07663.rjw@sisk.pl>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1376 bytes --]
applied
-- Len Brown, Intel Open Source Technology Center
On Mon, 29 Dec 2008, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rjw@sisk.pl>
>
> According to the ACPI specification the SCI_EN flag is controlled by
> the hardware, which sets this flag to inform the kernel that ACPI is
> enabled. For this reason, we shouldn't try to modify SCI_EN
> directly. Also, we don't need to do it in irqrouter_resume(), since
> lower-level resume code takes care of enabling ACPI in case it hasn't
> been enabled by the BIOS before passing control to the kernel (which
> by the way is against the ACPI specification).
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> ---
> drivers/acpi/pci_link.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> Index: linux-2.6/drivers/acpi/pci_link.c
> ===================================================================
> --- linux-2.6.orig/drivers/acpi/pci_link.c
> +++ linux-2.6/drivers/acpi/pci_link.c
> @@ -793,10 +793,6 @@ static int irqrouter_resume(struct sys_d
> struct list_head *node = NULL;
> struct acpi_pci_link *link = NULL;
>
> -
> - /* Make sure SCI is enabled again (Apple firmware bug?) */
> - acpi_set_register(ACPI_BITREG_SCI_ENABLE, 1);
> -
> list_for_each(node, &acpi_link.entries) {
> link = list_entry(node, struct acpi_pci_link, node);
> if (!link) {
> --8323328-415918257-1230681806=:17126--
prev parent reply other threads:[~2008-12-31 0:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 18:19 Rafael J. Wysocki
2008-12-29 21:16 ` Maxim Levitsky
2008-12-30 21:59 ` Rafael J. Wysocki
2008-12-30 22:33 ` Maxim Levitsky
2008-12-31 0:03 ` Len Brown [this message]
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=alpine.LFD.2.00.0812301903210.17126@localhost.localdomain \
--to=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®