1. 21 8月, 2009 1 次提交
  2. 29 7月, 2009 1 次提交
    • S
      sh: Rework irqflags tracing to fix up CONFIG_PROVE_LOCKING. · fd78a76a
      Stuart Menefy 提交于
      This cleans up the irqflags tracing code quite a bit and ties it
      in to various missing callsites that caused an imbalance when
      CONFIG_PROVE_LOCKING was enabled.
      
      Previously this was catching on:
      
       987 #ifdef CONFIG_PROVE_LOCKING
       988     DEBUG_LOCKS_WARN_ON(!p->hardirqs_enabled);
       989     DEBUG_LOCKS_WARN_ON(!p->softirqs_enabled);
       990 #endif
       991     retval = -EAGAIN;
      
      with hardirqs being doubly enabled, and subsequently bailing out
      with the following call trace:
      
      	Call trace:
      	[<88035224>] __lock_acquire+0x616/0x6a6
      	[<88015a8c>] do_fork+0xf8/0x2b0
      	[<880331ec>] trace_hardirqs_on_caller+0xd4/0x114
      	[<88241074>] _spin_unlock_irq+0x20/0x64
      	[<88035224>] __lock_acquire+0x616/0x6a6
      	[<8800386c>] kernel_thread+0x48/0x70
      	[<88024ecc>] ____call_usermodehelper+0x0/0x110
      	[<88024ecc>] ____call_usermodehelper+0x0/0x110
      	[<88003894>] kernel_thread_helper+0x0/0x14
      	[<88024bac>] __call_usermodehelper+0x38/0x70
      	[<88025dc0>] worker_thread+0x150/0x274
      	[<88035b9c>] lock_release+0x0/0x198
      	[<88024b74>] __call_usermodehelper+0x0/0x70
      	[<88028cf0>] autoremove_wake_function+0x0/0x30
      	[<88028bf2>] kthread+0x3e/0x70
      	[<88025c70>] worker_thread+0x0/0x274
      	[<8800389c>] kernel_thread_helper+0x8/0x14
      	[<88028bb4>] kthread+0x0/0x70
      	[<88003894>] kernel_thread_helper+0x0/0x14
      Reported-by: NNobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
      Signed-off-by: NStuart Menefy <stuart.menefy@st.com>
      Signed-off-by: NMatt Fleming <matt@console-pimps.org>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      fd78a76a
  3. 07 7月, 2009 1 次提交
  4. 03 7月, 2009 1 次提交
    • M
      sh-sci: update receive error handling for muxed irqs · 44e18e9e
      Magnus Damm 提交于
      This patch updates the receive error code for muxed
      interrupts in the sh-sci driver.
      
      Receive error interrupts may be generated by the hardware
      if RE or REIE bits in SCSCR are set. Update the muxed
      interrupt handling code to acknowledge error interrupts
      if RE or REIE is set, instead of only acknowledging if
      REIE is set.
      
      Without this patch error interrupts may be generated but
      never acked resulting in a "nobody cared" crash.
      Signed-off-by: NMagnus Damm <damm@igel.co.jp>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      44e18e9e
  5. 15 6月, 2009 1 次提交
  6. 02 6月, 2009 1 次提交
  7. 13 5月, 2009 1 次提交
  8. 08 5月, 2009 10 次提交
  9. 07 5月, 2009 1 次提交
    • P
      sh: Integrate the SH-5 onchip_remap() more coherently. · 0fb849b9
      Paul Mundt 提交于
      Presently this is special-cased for early initialization. While there are
      situations where these static early initializations are still necessary,
      with minor changes it is possible to use this for the regular ioremap
      implementation as well. This allows us to kill off the special-casing for
      the remap completely and to start tidying up all of the SH-5
      special-casing in drivers.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      0fb849b9
  10. 03 3月, 2009 1 次提交
  11. 27 2月, 2009 1 次提交
  12. 22 12月, 2008 8 次提交
  13. 13 11月, 2008 1 次提交
  14. 12 11月, 2008 1 次提交
  15. 31 10月, 2008 1 次提交
  16. 16 10月, 2008 1 次提交
  17. 02 10月, 2008 2 次提交
  18. 01 10月, 2008 1 次提交
  19. 08 9月, 2008 1 次提交
  20. 28 7月, 2008 1 次提交
  21. 21 7月, 2008 1 次提交
  22. 16 5月, 2008 1 次提交
  23. 08 5月, 2008 1 次提交