linux-toradex.git/drivers/char/hpet.c, branch v2.6.30.6

clocksource: pass clocksource to read() callback

2009-04-21T20:41:47+00:00

Pass clocksource pointer to the read() callback for clocksources.  This
allows us to share the callback between multiple instances.

[hugh@veritas.com: fix powerpc build of clocksource pass clocksource mods]
[akpm@linux-foundation.org: cleanup]
Signed-off-by: Magnus Damm 
Acked-by: John Stultz 
Cc: Thomas Gleixner 
Signed-off-by: Hugh Dickins 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

hpet: fix the possibility of insane return value of hpet_calibrate() against SMI

2009-04-03T02:05:01+00:00

hpet_calibrate() has a possibility of miss-calibration due to SMI.  If SMI
interrupts in the while loop of calibration, then return value will be
big.  This change calibrates until stabilizing by the return value with a
small value.

[akpm@linux-foundation.org: trivial style tweaks]
Signed-off-by: Yasunori Goto 
Acked-by: Clemens Ladisch 
Acked-by: Vojtech Pavlik 
Cc: Robert Picco 
Cc: Venkatesh Pallipadi 
Cc: Ingo Molnar 
Acked-by: Paul Gortmaker 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

x86: correct link to HPET timer specification

2008-11-24T09:05:12+00:00

Impact: update documentation / help text

Original link is dead.

Signed-off-by: Denis V. Lunev 
Signed-off-by: Ingo Molnar

saner FASYNC handling on file close

2008-11-01T16:49:46+00:00

As it is, all instances of ->release() for files that have ->fasync()
need to remember to evict file from fasync lists; forgetting that
creates a hole and we actually have a bunch that *does* forget.

So let's keep our lives simple - let __fput() check FASYNC in
file->f_flags and call ->fasync() there if it's been set.  And lose that
crap in ->release() instances - leaving it there is still valid, but we
don't have to bother anymore.

Signed-off-by: Al Viro 
Signed-off-by: Linus Torvalds

drivers/char: use nr_irqs

2008-10-16T14:52:05+00:00

convert them to nr_irqs.

Signed-off-by: Yinghai Lu 
Signed-off-by: Ingo Molnar

HPET: Remove spurious HPET busy warning message.

2008-10-10T07:25:43+00:00

On x86 systems with CONFIG_HPET_TIMER enabled, when
the HPET driver (drivers/char/hpet.c) is loaded,
an incorrect busy message is printed when the driver
initializes since the HPET has already been allocated
by the core timer code. Remove the warning message.

Signed-off-by: David John 
Acked-by: Venkatesh Pallipadi 
Signed-off-by: Ingo Molnar

hpet: /dev/hpet - fixes and cleanup, fix

2008-07-31T20:49:58+00:00

fix:

On Thursday 31 July 2008, Ingo Molnar wrote:
>   drivers/built-in.o: In function `hpet_alloc':
>   : undefined reference to `__udivdi3'
>   drivers/built-in.o: In function `hpet_alloc':
>   : undefined reference to `__umoddi3'

Signed-off-by: David Brownell 
Signed-off-by: Ingo Molnar

hpet: /dev/hpet - fixes and cleanup

2008-07-31T16:45:41+00:00

Minor /dev/hpet updates and bugfixes:

  * Remove dead code, mostly remnants of an incomplete/unusable
    kernel interface ... noted when addressing "sparse" warnings:
      + hpet_unregister() and a routine it calls
      + hpet_task and all references, including hpet_task_lock
      + hpet_data.hd_flags (and HPET_DATA_PLATFORM)

  * Correct and improve boot message:
      + displays *counter* (shared between comparators) bit width,
        not *timer* bit widths (which are often mixed)
      + relabel "timers" as "comparators"; this is less confusing,
        they are not independent like normal timers are (sigh)
      + display MHz not Hz; it's never less than 10 MHz.

  * Tighten and correct the userspace interface code
      + don't accidentally program comparators in 64-bit mode using
        32-bit values ... always force comparators into 32-bit mode
      + provide the correct bit definition flagging comparators with
        periodic capability ... the ABI is unchanged

  * Update Documentation/hpet.txt
      + be more correct and current
      + expand description a bit
      + don't mention that now-gone kernel interface

Plus, add a FIXME comment for something that could cause big trouble
on systems with more capable HPETs than at least Intel seems to ship.

It seems that few folk use this userspace interface; it's not very
usable given the general lack of HPET IRQ routing.  I'm told that
the only real point of it any more is to mmap for fast timestamps;
IMO that's handled better through the gettimeofday() vsyscall.

Signed-off-by: David Brownell 
Acked-by: Clemens Ladisch 
Signed-off-by: Ingo Molnar

Merge branch 'linus' into timers/hpet

2008-07-31T16:43:41+00:00

#if 0 hpet_unregister()

2008-07-25T17:53:43+00:00

This patch #if 0's the unused hpet_unregister().

Signed-off-by: Adrian Bunk 
Acked-by: Clemens Ladisch 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds