public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Len Brown <lenb@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [git pull request] ACPI patches for 2.6.34-rc6
Date: Tue, 11 May 2010 10:42:52 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.1005111031260.3711@i5.linux-foundation.org> (raw)
In-Reply-To: <20100511172543.GA17868@srcf.ucam.org>



On Tue, 11 May 2010, Matthew Garrett wrote:
> 
> I've now checked the behaviour of Windows. It turns out that it never 
> makes the ACPI enable SMM call on resume. This is consistent with 
> http://bugzilla.kernel.org/show_bug.cgi?id=13745 which shows a bug 
> being introduced by us making the enable call in the first place. 
> Merging my patch and removing the blacklist would re-break these 
> machines. Instead, we should just unconditionally set SCI_EN since this 
> is the tested configuration. I'll send a followup patch.

Hmm. But that's the thing that Rafael claims doesn't work on his machine. 

Maybe windows does something else? Or do you _see_ windows doing that 
write?

Note that our acpi_enable() won't do anything either if the machine comes 
up in ACPI mode, so maybe you checked the behavior on that kind of 
machine, and Windows does the same? IOW, if acpi_hw_get_mode() already 
returns ACPI_SYS_MODE_ACPI, the whole thing is a no-op.

Finally, it's possible that we really should just write the dang SCI_EN 
bit directly, but that what we do wrong is that doing so with

	acpi_write_bit_register()

will write it _even_if_ the bit was already set. That could explain 
Rafael's problems too - writing the register directly may be the 
RightThing(tm), but writing it if the bit was already set may well cause 
some confusion.

				Linus

  reply	other threads:[~2010-05-11 17:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07  2:22 [git pull request] ACPI patches for 2.6.34-rc6 Len Brown
2010-05-07  2:34 ` Linus Torvalds
2010-05-07  6:12   ` Matthew Garrett
2010-05-07 21:06     ` Linus Torvalds
2010-05-07 21:13       ` Matthew Garrett
2010-05-07 21:21         ` Linus Torvalds
2010-05-07 21:36           ` Matthew Garrett
2010-05-11 17:25             ` Matthew Garrett
2010-05-11 17:42               ` Linus Torvalds [this message]
2010-05-11 17:59                 ` Matthew Garrett
2010-05-11 18:17                   ` Linus Torvalds
2010-05-11 18:22                     ` Matthew Garrett
2010-05-12 16:07               ` Robert Wörle
2010-05-12 16:12                 ` Matthew Garrett
2010-05-07 22:39   ` Rafael J. Wysocki
2010-05-07 23:00     ` Linus Torvalds
2010-05-07 23:17       ` Rafael J. Wysocki
2010-05-07 23:21         ` Linus Torvalds
2010-05-08  0:03           ` Rafael J. Wysocki
2010-05-08  0:10             ` Linus Torvalds
2010-05-08  5:19               ` Len Brown

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.1005111031260.3711@i5.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox