28 Sep, 2011

1 commit

  • There are numerous broken references to Documentation files (in other
    Documentation files, in comments, etc.). These broken references are
    caused by typo's in the references, and by renames or removals of the
    Documentation files. Some broken references are simply odd.

    Fix these broken references, sometimes by dropping the irrelevant text
    they were part of.

    Signed-off-by: Paul Bolle
    Signed-off-by: Jiri Kosina

    Paul Bolle
     

17 May, 2011

1 commit


02 Nov, 2010

1 commit

  • "gadget", "through", "command", "maintain", "maintain", "controller", "address",
    "between", "initiali[zs]e", "instead", "function", "select", "already",
    "equal", "access", "management", "hierarchy", "registration", "interest",
    "relative", "memory", "offset", "already",

    Signed-off-by: Uwe Kleine-König
    Signed-off-by: Jiri Kosina

    Uwe Kleine-König
     

27 Oct, 2010

1 commit


04 Aug, 2010

1 commit

  • This file seeks to explain the nuances in various delays;
    many driver writers are not necessarily familiar with the
    various kernel timers, their shortfalls, and quirks. When
    faced with

    ndelay, udelay, mdelay, usleep_range, msleep, and msleep_interrubtible

    the question "How do I just wait 1 ms for my hardware to
    latch?" has the non-intuitive "best" answer:
    usleep_range(1000,1500)

    This patch is followed by a series of checkpatch additions
    that seek to help kernel hackers pick the best delay.

    Signed-off-by: Patrick Pannuto
    Cc: apw@canonical.com
    Cc: corbet@lwn.net
    Cc: arjan@linux.intel.com
    Cc: Randy Dunlap
    Cc: Andrew Morton
    LKML-Reference:
    Signed-off-by: Thomas Gleixner

    Patrick Pannuto
     

02 Jun, 2010

1 commit


24 May, 2010

1 commit


13 Mar, 2010

1 commit

  • Documentation/timers/hpet.txt:
    Expose example and tool source files in the Documentation/timers/ directory in
    their own files instead of being buried (almost hidden) in readme/txt files.
    This should help to prevent bitrot.

    This will make them more visible/usable to users who may need
    to use them, to developers who may need to test with them, and
    to anyone who would fix/update them if they were more visible.

    Also, if any of these possibly should not be in the kernel tree at
    all, it will be clearer that they are here and we can discuss if
    they should be removed.

    Signed-off-by: Randy Dunlap
    Cc: Thomas Gleixner
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Randy Dunlap
     

09 Nov, 2009

1 commit

  • That URL is out of date. Update it.

    Cc: Thomas Gleixner
    Cc: Randy Dunlap
    Cc: Matt LaPlante
    Cc: Jiri Kosina
    Signed-off-by: WANG Cong
    Acked-by: Matt LaPlante
    Signed-off-by: Jiri Kosina

    Amerigo Wang
     

13 Jun, 2009

1 commit


01 Aug, 2008

2 commits

  • 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

    David Brownell
     
  • Ingo Molnar
     

27 Jul, 2008

1 commit


24 Jul, 2008

1 commit


17 Apr, 2008

1 commit