From: Len Brown <lenb@kernel.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Linux Power Management List <linux-pm@lists.osdl.org>,
linux-pci@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] intel_idle: PCI quirk to prevent Lenovo Ideapad s10-3 boot hang
Date: Sat, 16 Oct 2010 04:25:59 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1010160416340.2238@localhost.localdomain> (raw)
In-Reply-To: <20101005114047.GA29495@srcf.ucam.org>
> > > > we check (and clear) that bit only if the acpi tables
> > > > tell us to do so.
> > >
> > > Do the tables tell us to do so on this platform?
> >
> > In this configuration, yes, otherwise acpi_idle
> > would have failed in exactly the same way.
>
> So why is intel_idle not paying attention to what the platform is
> requesting?
ACPI's BM_STS mechanism is obsolete, and is fundmentally
incompatible with a tickless OS. The status bit is a NO-OP
on most modern chip-sets under normal conditions.
However, even when not a NO-OP, it is supposed to
be just an indicator and clearing it should have
no functional effect on the hardware except to
re-arm the hardware that looks for BM_STS.
Clearing BM_STS on the NM10 chipset at boot-time to
make the system boot has nothing to do with
"what the platform is requesting".
It is a workaround for a platform bug that is randomly
masked by how the behaviour of the legacy ACPI OS.
intel_idle it knows nothing about ACPI, and it never will.
thanks,
Len Brown, Intel Open Source Technology Center
prev parent reply other threads:[~2010-10-16 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 1:26 [PATCH] intel_idle: PCI quirk to prevent Lenovo Ideapad s10-3 boot hang Len Brown
2010-09-27 13:57 ` Matthew Garrett
2010-09-30 22:14 ` Len Brown
2010-09-30 22:29 ` Matthew Garrett
2010-10-05 5:06 ` Len Brown
2010-10-05 11:40 ` Matthew Garrett
2010-10-16 8:25 ` 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.1010160416340.2238@localhost.localdomain \
--to=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.osdl.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