1. 12 Jul, 2011 3 commits
    • Haojian Zhuang's avatar
      ARM: pxa: add clk_set_rate() · 52585ccd
      Haojian Zhuang authored
      Since there're mulitple clock rates in some device controllers, enable
      clk_set_rate() for this usage.
      Signed-off-by: default avatarHaojian Zhuang <haojian.zhuang@marvell.com>
      Signed-off-by: default avatarEric Miao <eric.y.miao@gmail.com>
      52585ccd
    • Eric Miao's avatar
      ARM: pxa: enable AUTO_ZRELADDR · 4e234cc0
      Eric Miao authored
      Signed-off-by: default avatarEric Miao <eric.y.miao@gmail.com>
      4e234cc0
    • Russell King - ARM Linux's avatar
      ARM: introduce handle_IRQ() not to dump exception stack · a4841e39
      Russell King - ARM Linux authored
      On Mon, Jul 11, 2011 at 3:52 PM, Russell King - ARM Linux
      <linux@arm.linux.org.uk> wrote:
      
      ...
      
      > The __exception annotation on a function causes this to happen:
      >
      > [<c002406c>] (asm_do_IRQ+0x6c/0x8c) from [<c0024b84>]
      > (__irq_svc+0x44/0xcc)
      > Exception stack(0xc3897c78 to 0xc3897cc0)
      > 7c60:                                                       4022d320 4022e000
      > 7c80: 08000075 00001000 c32273c0 c03ce1c0 c2b49b78 4022d000 c2b420b4 00000001
      > 7ca0: 00000000 c3897cfc 00000000 c3897cc0 c00afc54 c002edd8 00000013 ffffffff
      >
      > Where that stack dump represents the pt_regs for the exception which
      > happened.  Any function found in while unwinding will cause this to
      > be printed.
      >
      > If you insert a C function between the IRQ assembly and asm_do_IRQ,
      > the
      > dump you get from asm_do_IRQ will be the stack for your function,
      > not
      > the pt_regs.  That makes the feature useless.
      >
      
      When __irq_svc - or any of the other exception handling assembly code -
      calls the C code, the stack pointer will be pointing at the pt_regs
      structure.
      
      All the entry points into C code from the exception handling code are
      marked with __exception or __exception_irq_enter to indicate that they
      are one of the functions which has pt_regs above them.
      
      Normally, when you've entered asm_do_IRQ() you will have this stack
      layout (higher address towards top):
      
             pt_regs
             asm_do_IRQ frame
      
      If you insert a C function between the exception assembly code and
      asm_do_IRQ, you end up with this stack layout instead:
      
             pt_regs
             your function frame
             asm_do_IRQ frame
      
      This means when we unwind, we'll get to asm_do_IRQ, and rather than
      dumping out the pt_regs, we'll dump out your functions stack frame
      instead, because that's what is above the asm_do_IRQ stack frame
      rather than the expected pt_regs structure.
      
      The fix is to introduce handle_IRQ() for no exception stack dump, so
      it can be called with MULTI_IRQ_HANDLER is selected and a C function
      is between the assembly code and the actual IRQ handling code.
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: default avatarEric Miao <eric.y.miao@gmail.com>
      a4841e39
  2. 04 Jul, 2011 7 commits
  3. 03 Jul, 2011 30 commits