17 May, 2011

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