linux.git/drivers/clocksource, branch v2.6.27-rc4

Fix printk format warning in clocksource/acpi_pm.c

2008-07-15T18:01:39+00:00

For real, this time.  The earlier attempt just moved the warning around.

Signed-off-by: Linus Torvalds

acpi_pm clccksource: fix printk format warning

2008-07-12T03:29:08+00:00

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 
Cc: akpm 
Signed-off-by: Thomas Gleixner

pmtmr: allow command line override of ioport

2008-07-10T05:10:00+00:00

Stupid BIOSes do not tell us about the PMTimer, 
but we might know where it is.

Signed-off-by: Thomas Gleixner

tclib: Fix compile warnings

2008-03-13T21:53:29+00:00

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

atmel_tc clocksource/clockevent code

2008-03-04T12:42:24+00:00

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 
Signed-off-by: Haavard Skinnemoen

x86_64: fix typo in acpi_pm.c

2007-07-22T01:37:12+00:00

Signed-off-by: Alessio Igor Bogani 
Cc: john stultz 
Signed-off-by: Andrew Morton 
Signed-off-by: Andi Kleen 
Signed-off-by: Linus Torvalds

PCI: Change all drivers to use pci_device->revision

2007-07-11T23:02:10+00:00

Instead of all drivers reading pci config space to get the revision
ID, they can now use the pci_device->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 
Acked-by: Dave Jones 
Signed-off-by: Greg Kroah-Hartman

ACPI: correct pathname in comment

2007-04-25T18:27:06+00:00

Signed-off-by: Daniel Walker 
Signed-off-by: Andrew Morton 
Signed-off-by: Len Brown

[PATCH] correct slow acpi_pm rating

2007-03-27T16:05:15+00:00

On Bob's machine clocksource is selecting PIT over the ACPI PM timer,
because he has the PIIX4 bug.  That bug drops the ACPI PM timers rating
to the same as the PIT, so that's why you're getting the PIT.

Realistically, the PIT is much slower then even the triple read ACPI PM,
so the de-ranking code is probably dropping it too far.

So don't drop ACPI PM quite so low if we see the PIIX4 bug.

Signed-off-by: John Stultz 
Cc: Bob Tracy 
Cc: Ingo Molnar 
Cc: Thomas Gleixner 
Cc: Andi Kleen 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] clocksource init adjustments (fix bug #7426)

2007-03-05T15:57:53+00:00

This patch resolves the issue found here:
http://bugme.osdl.org/show_bug.cgi?id=7426

The basic summary is:
Currently we register most of i386/x86_64 clocksources at module_init
time. Then we enable clocksource selection at late_initcall time. This
causes some problems for drivers that use gettimeofday for init
calibration routines (specifically the es1968 driver in this case),
where durring module_init, the only clocksource available is the low-res
jiffies clocksource. This may cause slight calibration errors, due to
the small sampling time used.

It should be noted that drivers that require fine grained time may not
function on architectures that do not have better then jiffies
resolution timekeeping (there are a few). However, this does not
discount the reasonable need for such fine-grained timekeeping at init
time.

Thus the solution here is to register clocksources earlier (ideally when
the hardware is being initialized), and then we enable clocksource
selection at fs_initcall (before device_initcall).

This patch should probably get some testing time in -mm, since
clocksource selection is one of the most important issues for correct
timekeeping, and I've only been able to test this on a few of my own
boxes.

Signed-off-by: John Stultz 
Cc: Thomas Gleixner 
Cc: Ingo Molnar 
Cc: "David S. Miller" 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds