<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/clocksource, branch v2.6.27.6</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/clocksource?h=v2.6.27.6</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/clocksource?h=v2.6.27.6'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2008-09-11T09:14:29Z</updated>
<entry>
<title>clocksource, acpi_pm.c: fix check for monotonicity</title>
<updated>2008-09-11T09:14:29Z</updated>
<author>
<name>Dominik Brodowski</name>
<email>linux@dominikbrodowski.net</email>
</author>
<published>2008-09-11T09:09:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f1926ce63b996b42772b39e4b47bb4ef4ba748b4'/>
<id>urn:sha1:f1926ce63b996b42772b39e4b47bb4ef4ba748b4</id>
<content type='text'>
Actually check the monotonicity of the ACPI PMTMR ten times, only delay for
0.9 miliseconds at most, and bail out early if some problem is determined.

Reported-by: Jochen Voß &lt;jochen.voss@googlemail.com&gt;
Signed-off-by: Dominik Brodowski &lt;linux@dominikbrodowski.net&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>clocksource, acpi_pm.c: check for monotonicity</title>
<updated>2008-09-06T13:33:33Z</updated>
<author>
<name>Dominik Brodowski</name>
<email>linux@dominikbrodowski.net</email>
</author>
<published>2008-09-05T21:05:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4ab6a219113197425ac112e35e1ec8062c69888e'/>
<id>urn:sha1:4ab6a219113197425ac112e35e1ec8062c69888e</id>
<content type='text'>
The current check for monotonicity is way too weak: Andreas Mohr reports (
http://lkml.org/lkml/2008/8/10/77 ) that on one of his test systems the
current check only triggers in 50% of all cases, leading to catastrophic
timer behaviour.  To fix this issue, expand the check for monotonicity by
doing ten consecutive tests instead of one.

Signed-off-by: Dominik Brodowski &lt;linux@dominikbrodowski.net&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>clocksource, acpi_pm.c: use proper read function also in errata mode</title>
<updated>2008-09-06T13:33:31Z</updated>
<author>
<name>Dominik Brodowski</name>
<email>linux@dominikbrodowski.net</email>
</author>
<published>2008-09-05T21:05:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dfdf748a61a21b7397b9f57c83de722de71dc56a'/>
<id>urn:sha1:dfdf748a61a21b7397b9f57c83de722de71dc56a</id>
<content type='text'>
On all hardware (some Intel ICH4, PIIX4 and PIIX4E chipsets) affected by a
hardware errata there's about a 4.2% chance that initialization of the
ACPI PMTMR fails.  On those chipsets, we need to read out the timer value
at least three times to get a correct result, for every once in a while
(i.e.  within a 3 ns window every 69.8 ns) the read returns a bogus
result.  During normal operation we work around this issue, but during
initialization reading a bogus value may lead to -EINVAL even though the
hardware is usable.

Thanks to Andreas Mohr for spotting this issue.

Signed-off-by: Dominik Brodowski &lt;linux@dominikbrodowski.net&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>Fix printk format warning in clocksource/acpi_pm.c</title>
<updated>2008-07-15T18:01:39Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2008-07-15T18:01:39Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=14351760e314b8a9720804b11c6bd11d0c0b1258'/>
<id>urn:sha1:14351760e314b8a9720804b11c6bd11d0c0b1258</id>
<content type='text'>
For real, this time.  The earlier attempt just moved the warning around.

Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>acpi_pm clccksource: fix printk format warning</title>
<updated>2008-07-12T03:29:08Z</updated>
<author>
<name>Randy Dunlap</name>
<email>randy.dunlap@oracle.com</email>
</author>
<published>2008-07-11T19:57:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=38032f72601deac7aab00691c79e83d09b204e2a'/>
<id>urn:sha1:38032f72601deac7aab00691c79e83d09b204e2a</id>
<content type='text'>
Fix printk format warning in acpi_pm clocksource:

linux-next-20080711/drivers/clocksource/acpi_pm.c:231: warning: format '%04lx' expects type 'long unsigned int', but argument 2 has type 'u32'

Signed-off-by: Randy Dunlap &lt;randy.dunlap@oracle.com&gt;
Cc: akpm &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
</content>
</entry>
<entry>
<title>pmtmr: allow command line override of ioport</title>
<updated>2008-07-10T05:10:00Z</updated>
<author>
<name>Thomas Gleixner</name>
<email>tglx@linutronix.de</email>
</author>
<published>2008-05-21T19:14:58Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6b148507d3d042a3c11f4c3f6c0f649c6a89220d'/>
<id>urn:sha1:6b148507d3d042a3c11f4c3f6c0f649c6a89220d</id>
<content type='text'>
Stupid BIOSes do not tell us about the PMTimer, 
but we might know where it is.

Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
</content>
</entry>
<entry>
<title>tclib: Fix compile warnings</title>
<updated>2008-03-13T21:53:29Z</updated>
<author>
<name>David Brownell</name>
<email>david-b@pacbell.net</email>
</author>
<published>2008-03-13T17:44:48Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3ee08aea72f44a6d176af7a97f3ad0c67bc65a44'/>
<id>urn:sha1:3ee08aea72f44a6d176af7a97f3ad0c67bc65a44</id>
<content type='text'>
Does that have something analagous to this "remove warnings" patch?
Seems setup_clkevents() no longer needs a t0_clk parameter either...

Signed-off-by: Haavard Skinnemoen &lt;hskinnemoen@atmel.com&gt;
</content>
</entry>
<entry>
<title>atmel_tc clocksource/clockevent code</title>
<updated>2008-03-04T12:42:24Z</updated>
<author>
<name>David Brownell</name>
<email>david-b@pacbell.net</email>
</author>
<published>2008-02-23T01:28:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4d243f92e48a7913938f48fa9ebea5239168bb11'/>
<id>urn:sha1:4d243f92e48a7913938f48fa9ebea5239168bb11</id>
<content type='text'>
Clocksource and clockevent device based on the Atmel TC blocks.

The clockevent device handles both periodic and oneshot modes, so this
enables NO_HZ and high res timers on some platforms that previously
couldn't use those mechanisms.

This works on both AVR32 and AT91 chips, given relevant patches for
tclib support (always) and clockevents (or else this will only look
like a higher precision clocksource).  It's an updated and modularized
version of an AT91-only patch that has circulated for some time now.

Changes relative to the original patch:
  * Update to use new tclib API
  * Replace open-coded do-while loop using goto with a real do-while loop
  * Minor irq handler optimization: Load register base address from
    dev_id instead of a global variable.
  * Aggressively turn off clocks when the clockevent isn't being used
  * Include the clockevent code on AT91RM9200 as well. The rating is
    lower than the System Timer, so the clock will usually stay off.
  * Don't assume that the number of clocks is always equal to the
    number of irqs.

Signed-off-by: David Brownell &lt;dbrownell@users.sourceforge.net&gt;
Signed-off-by: Haavard Skinnemoen &lt;hskinnemoen@atmel.com&gt;
</content>
</entry>
<entry>
<title>x86_64: fix typo in acpi_pm.c</title>
<updated>2007-07-22T01:37:12Z</updated>
<author>
<name>Alessio Igor Bogani</name>
<email>abogani@texware.it</email>
</author>
<published>2007-07-21T15:11:19Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7b0b8207e07f3f3ce01af37b78024c60e9f4b1f5'/>
<id>urn:sha1:7b0b8207e07f3f3ce01af37b78024c60e9f4b1f5</id>
<content type='text'>
Signed-off-by: Alessio Igor Bogani &lt;abogani@texware.it&gt;
Cc: john stultz &lt;johnstul@us.ibm.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Andi Kleen &lt;ak@suse.de&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>PCI: Change all drivers to use pci_device-&gt;revision</title>
<updated>2007-07-11T23:02:10Z</updated>
<author>
<name>Auke Kok</name>
<email>auke-jan.h.kok@intel.com</email>
</author>
<published>2007-06-08T22:46:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=44c10138fd4bbc4b6d6bff0873c24902f2a9da65'/>
<id>urn:sha1:44c10138fd4bbc4b6d6bff0873c24902f2a9da65</id>
<content type='text'>
Instead of all drivers reading pci config space to get the revision
ID, they can now use the pci_device-&gt;revision member.

This exposes some issues where drivers where reading a word or a dword
for the revision number, and adding useless error-handling around the
read. Some drivers even just read it for no purpose of all.

In devices where the revision ID is being copied over and used in what
appears to be the equivalent of hotpath, I have left the copy code
and the cached copy as not to influence the driver's performance.

Compile tested with make all{yes,mod}config on x86_64 and i386.

Signed-off-by: Auke Kok &lt;auke-jan.h.kok@intel.com&gt;
Acked-by: Dave Jones &lt;davej@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
</feed>
