[lkml]   [2011]   [Apr]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCHv5 2/3] ARM: Allow machines to override __delay()
    On 04/06/2011 01:56 AM, Stephen Boyd wrote:
    > Some machines want to implement their own __delay() routine based
    > on fixed rate timers. Expose functionality to set the __delay()
    > routine at runtime. This should allow two machines with different
    > __delay() routines to happily co-exist within the same kernel
    > with minimal overhead.
    > Russell expressed concern that using a timer based __delay()
    > would cause problems when an iomapped device isn't mapped in
    > prior to a delay call being made (see
    > for
    > more info). We can sidestep that issue with this approach since
    > the __delay() routine_should_ only be pointed to a timer based
    > delay once the timer has been properly mapped. Up until that
    > point __delay() and udelay() will use delay_loop() which is
    > always safe to call.
    > This patch is inspired by x86's delay.c

    Tested-by: Mattias Wallin <>

    Mattias Wallin

     \ /
      Last update: 2011-04-07 22:53    [W:0.021 / U:5.480 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site