Skip to content
  1. Aug 11, 2012
    • Colin Cross's avatar
      ARM: 7486/1: sched_clock: update epoch_cyc on resume · 237ec6f2
      Colin Cross authored
      
      
      Many clocks that are used to provide sched_clock will reset during
      suspend.  If read_sched_clock returns 0 after suspend, sched_clock will
      appear to jump forward.  This patch resets cd.epoch_cyc to the current
      value of read_sched_clock during resume, which causes sched_clock() just
      after suspend to return the same value as sched_clock() just before
      suspend.
      
      In addition, during the window where epoch_ns has been updated before
      suspend, but epoch_cyc has not been updated after suspend, it is unknown
      whether the clock has reset or not, and sched_clock() could return a
      bogus value.  Add a suspended flag, and return the pre-suspend epoch_ns
      value during this period.
      
      The new behavior is triggered by calling setup_sched_clock_needs_suspend
      instead of setup_sched_clock.
      
      Signed-off-by: default avatarColin Cross <ccross@android.com>
      Reviewed-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      237ec6f2
  2. Jul 31, 2012
  3. Jul 30, 2012
  4. Jul 29, 2012
  5. Jul 28, 2012
  6. Jul 24, 2012
  7. Jul 09, 2012
  8. Jul 05, 2012
    • Russell King's avatar
      ARM: fix warnings about atomic64_read · b89d607b
      Russell King authored
      
      
      Fix:
      net/netfilter/xt_connbytes.c: In function 'connbytes_mt':
      net/netfilter/xt_connbytes.c:43: warning: passing argument 1 of 'atomic64_read' discards qualifiers from pointer target type
      ...
      
      by adding the missing const.
      
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      b89d607b
    • Will Deacon's avatar
      ARM: 7443/1: Revert "new way of handling ERESTART_RESTARTBLOCK" · 433e2f30
      Will Deacon authored
      
      
      This reverts commit 6b5c8045.
      
      Conflicts:
      
      	arch/arm/kernel/ptrace.c
      
      The new syscall restarting code can lead to problems if we take an
      interrupt in userspace just before restarting the svc instruction. If
      a signal is delivered when returning from the interrupt, the
      TIF_SYSCALL_RESTARTSYS will remain set and cause any syscalls executed
      from the signal handler to be treated as a restart of the previously
      interrupted system call. This includes the final sigreturn call, meaning
      that we may fail to exit from the signal context. Furthermore, if a
      system call made from the signal handler requires a restart via the
      restart_block, it is possible to clear the thread flag and fail to
      restart the originally interrupted system call.
      
      The right solution to this problem is to perform the restarting in the
      kernel, avoiding the possibility of handling a further signal before the
      restart is complete. Since we're almost at -rc6, let's revert the new
      method for now and aim for in-kernel restarting at a later date.
      
      Acked-by: default avatarCatalin Marinas <catalin.marinas@arm.com>
      Signed-off-by: default avatarWill Deacon <will.deacon@arm.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      433e2f30
    • Russell King's avatar
      ARM: fix set_domain() macro · 82401bf1
      Russell King authored
      
      
      Avoid polluting drivers with a set_domain() macro, which interferes with
      structure member names:
      
      drivers/net/wireless/ath/ath9k/dfs_pattern_detector.c:294:33: error: macro "set_domain" passed 2 arguments, but takes just 1
      
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      82401bf1
  9. Jul 01, 2012
    • Shawn Guo's avatar
      ARM: fiq: change FIQ_START to a variable · bc89663a
      Shawn Guo authored
      
      
      The commit a2be01b1 (ARM: only include mach/irqs.h for !SPARSE_IRQ)
      makes mach/irqs.h only be included for !SPARSE_IRQ build.  There are
      a nubmer of platforms have FIQ_START defined in mach/irqs.h for FIQ
      support.
      
        arch/arm/mach-rpc/include/mach/irqs.h:#define FIQ_START         64
        arch/arm/mach-s3c24xx/include/mach/irqs.h:#define FIQ_START             IRQ_EINT0
        arch/arm/plat-mxc/include/mach/irqs.h:#define FIQ_START 0
      
      If SPARSE_IRQ is enabled for any of these platforms, the following
      compile error will be seen.
      
        arch/arm/kernel/fiq.c: In function ‘enable_fiq’:
        arch/arm/kernel/fiq.c:127:19: error: ‘FIQ_START’ undeclared (first use in this function)
        arch/arm/kernel/fiq.c:127:19: note: each undeclared identifier is reported only once for each function it appears in
        arch/arm/kernel/fiq.c: In function ‘disable_fiq’:
        arch/arm/kernel/fiq.c:132:20: error: ‘FIQ_START’ undeclared (first use in this function)
      
      The patch changes fiq code to have init_FIQ take FIQ_START from
      platforms as a parameter and assign it to variable fiq_start which
      is to replace FIQ_START uses in enable_fiq/disable_fiq.
      
      Signed-off-by: default avatarShawn Guo <shawn.guo@linaro.org>
      Cc: Kukjin Kim <kgene.kim@samsung.com>
      Cc: Sascha Hauer <s.hauer@pengutronix.de>
      Cc: Rob Herring <rob.herring@calxeda.com>
      Acked-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      bc89663a
  10. Jun 28, 2012
  11. Jun 20, 2012
  12. Jun 16, 2012
  13. May 31, 2012
  14. May 25, 2012
  15. May 21, 2012
  16. May 16, 2012
Loading