<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/include/acpi, branch linux-2.6.28.y</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=linux-2.6.28.y</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=linux-2.6.28.y'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2009-02-12T17:50:25+00:00</updated>
<entry>
<title>ACPI: Enable bit 11 in _PDC to advertise hw coord</title>
<updated>2009-02-12T17:50:25+00:00</updated>
<author>
<name>Pallipadi, Venkatesh</name>
<email>venkatesh.pallipadi@intel.com</email>
</author>
<published>2009-02-02T19:57:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=232d80938847060e01e894e6404ce162d4924954'/>
<id>urn:sha1:232d80938847060e01e894e6404ce162d4924954</id>
<content type='text'>
commit d96f94c604453f87fe24154b87e1e9a3a72511f8 upstream.

Bit 11 in intel PDC definitions is meant for OS capability to handle
hardware coordination of P-states. In Linux we have always supported
hwardware coordination of P-states. Just let the BIOSes know that we
support it, by setting this bit.

Some BIOSes use this bit to choose between hardware or software coordination
and without this change below, BIOSes switch to software coordination, which
is not very optimal in terms of power consumption and extra wakeups from idle.

Signed-off-by: Venkatesh Pallipadi &lt;venkatesh.pallipadi@intel.com&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ACPI: don't cond_resched() when irqs_disabled()</title>
<updated>2008-12-19T09:38:33+00:00</updated>
<author>
<name>Wu Fengguang</name>
<email>fengguang.wu@intel.com</email>
</author>
<published>2008-11-26T06:35:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=abe1dfab60e1839d115930286cb421f5a5b193f3'/>
<id>urn:sha1:abe1dfab60e1839d115930286cb421f5a5b193f3</id>
<content type='text'>
The ACPI interpreter usually runs with irqs enabled.
However, during suspend/resume it runs with
irqs disabled to evaluate _GTS/_BFS, as well as
by irqrouter_resume() which evaluates _CRS, _PRS, _SRS.

http://bugzilla.kernel.org/show_bug.cgi?id=12252

Signed-off-by: Wu Fengguang &lt;wfg@linux.intel.com&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
</content>
</entry>
<entry>
<title>ACPI: fix 2.6.28 acpi.debug_level regression</title>
<updated>2008-12-19T09:38:32+00:00</updated>
<author>
<name>Bjorn Helgaas</name>
<email>bjorn.helgaas@hp.com</email>
</author>
<published>2008-11-13T23:30:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=e76f42761197dd6e9405e2eeb35932acfede115a'/>
<id>urn:sha1:e76f42761197dd6e9405e2eeb35932acfede115a</id>
<content type='text'>
acpi_early_init() was changed to over-write the cmdline param,
making it really inconvenient to set debug flags at boot-time.

Also,
This sets the default level to "info", which is what all the ACPI
drivers use.  So to enable messages from drivers, you only have to
supply the "layer" (a.k.a. "component").  For non-"info" ACPI core
and ACPI interpreter messages, you have to supply both level and
layer masks, as before.

Signed-off-by: Bjorn Helgaas &lt;bjorn.helgaas@hp.com&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
</content>
</entry>
<entry>
<title>ACPICA: disable _BIF warning</title>
<updated>2008-11-27T07:17:30+00:00</updated>
<author>
<name>Lin Ming</name>
<email>ming.m.lin@intel.com</email>
</author>
<published>2008-11-27T06:42:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=e899b6485c332aa2d7510739507ab5e5d7b28e59'/>
<id>urn:sha1:e899b6485c332aa2d7510739507ab5e5d7b28e59</id>
<content type='text'>
A generic work-around from ACPICA is in the queue,
but since Linux has a work-around in its battery
driver, we can disable this warning now.

Allow _BIF method to return an Package with Buffer elements

http://bugzilla.kernel.org/show_bug.cgi?id=11822

Signed-off-by: Lin Ming &lt;ming.m.lin@intel.com&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
</content>
</entry>
<entry>
<title>ACPICA: Allow _WAK method to return an Integer</title>
<updated>2008-11-27T06:55:13+00:00</updated>
<author>
<name>Bob Moore</name>
<email>robert.moore@intel.com</email>
</author>
<published>2008-11-13T03:01:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=95a28ed08619cc70f31611886ac7b26ab0e462dc'/>
<id>urn:sha1:95a28ed08619cc70f31611886ac7b26ab0e462dc</id>
<content type='text'>
This can happen if the _WAK method returns nothing (as per ACPI
1.0) but does return an integer if the implicit return mechanism
is enabled.  This is the only method that has this problem,
since it is also defined to return a package of two integers
(ACPI 1.0b+). In all other cases, if a method returns an object
when one was not expected, no warning is issued.

Signed-off-by: Bob Moore &lt;robert.moore@intel.com&gt;
Signed-off-by: Lin Ming &lt;ming.m.lin@intel.com&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'ec' into release</title>
<updated>2008-11-12T02:17:26+00:00</updated>
<author>
<name>Len Brown</name>
<email>len.brown@intel.com</email>
</author>
<published>2008-11-12T02:17:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=d1876ba4dead6ace7e9fbf16f83397e6486d0dfe'/>
<id>urn:sha1:d1876ba4dead6ace7e9fbf16f83397e6486d0dfe</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'processor-256' into release</title>
<updated>2008-11-12T02:17:03+00:00</updated>
<author>
<name>Len Brown</name>
<email>len.brown@intel.com</email>
</author>
<published>2008-11-12T02:17:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=547f7847472c097a54adf38e6576f95ab512e27c'/>
<id>urn:sha1:547f7847472c097a54adf38e6576f95ab512e27c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'video' into release</title>
<updated>2008-11-12T02:15:50+00:00</updated>
<author>
<name>Len Brown</name>
<email>len.brown@intel.com</email>
</author>
<published>2008-11-12T02:15:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=f398778aa336a2919ee04ba45d915007230c6957'/>
<id>urn:sha1:f398778aa336a2919ee04ba45d915007230c6957</id>
<content type='text'>
Conflicts:
	Documentation/kernel-parameters.txt

Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'misc' into release</title>
<updated>2008-11-12T02:14:11+00:00</updated>
<author>
<name>Len Brown</name>
<email>len.brown@intel.com</email>
</author>
<published>2008-11-12T02:14:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=3e0fe364835cecc8560cf32bb9609f4c56c5d9fa'/>
<id>urn:sha1:3e0fe364835cecc8560cf32bb9609f4c56c5d9fa</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ACPICA: Use spinlock for acpi_{en|dis}able_gpe</title>
<updated>2008-11-11T23:35:42+00:00</updated>
<author>
<name>Alexey Starikovskiy</name>
<email>astarikovskiy@suse.de</email>
</author>
<published>2008-10-25T17:48:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=0b7084ac67fb84f0cf2f8bc02d7e0dea8521dd2d'/>
<id>urn:sha1:0b7084ac67fb84f0cf2f8bc02d7e0dea8521dd2d</id>
<content type='text'>
Disabling gpe might interfere with gpe detection/handling,
thus producing "interrupt not handled" errors.
Ironically, disabling of GPE from interrupt context is already
under spinlock, so only userspace needs to start using it.

Signed-off-by: Alexey Starikovskiy &lt;astarikovskiy@suse.de&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
</content>
</entry>
</feed>
