Eric Lee / smarc-fsl-linux-kernel

17 Jun, 2009

1 commit

  • 08604bd99   time: move PIT_TICK_RATE to linux/timex.h ... Browse Code »

    PIT_TICK_RATE is currently defined in four architectures, but in three
    different places. While linux/timex.h is not the perfect place for it, it
    is still a reasonable replacement for those drivers that traditionally use
    asm/timex.h to get CLOCK_TICK_RATE and expect it to be the PIT frequency.

    Note that for Alpha, the actual value changed from 1193182UL to 1193180UL.
    This is unlikely to make a difference, and probably can only improve
    accuracy. There was a discussion on the correct value of CLOCK_TICK_RATE
    a few years ago, after which every existing instance was getting changed
    to 1193182. According to the specification, it should be
    1193181.818181...

    Signed-off-by: Arnd Bergmann
    Cc: Richard Henderson
    Cc: Ivan Kokshaysky
    Cc: Ralf Baechle
    Cc: Benjamin Herrenschmidt
    Cc: Ingo Molnar
    Cc: Thomas Gleixner
    Cc: "H. Peter Anvin"
    Cc: Len Brown
    Cc: john stultz
    Cc: Dmitry Torokhov
    Cc: Takashi Iwai
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Arnd Bergmann
     

25 Jan, 2009

1 commit

  • e1b4d1143   x86: use standard PIT frequency ... Browse Code »

    the RDC and ELAN platforms use slighly different PIT clocks, resulting in
    a timex.h hack that changes PIT_TICK_RATE during build time. But if a
    tester enables any of these platform support .config options, the PIT
    will be miscalibrated on standard PC platforms.

    So use one frequency - in a subsequent patch we'll add a quirk to allow
    x86 platforms to define different PIT frequencies.

    Signed-off-by: Ingo Molnar

    Ingo Molnar
     

23 Oct, 2008

2 commits