1. 24 8月, 2011 1 次提交
  2. 12 8月, 2011 3 次提交
  3. 08 7月, 2011 1 次提交
    • S
      genirq: replace irq_gc_ack() with {set,clr}_bit variants (fwd) · 659fb32d
      Simon Guinot 提交于
      This fixes a regression introduced by e59347a1 "arm: orion:
      Use generic irq chip".
      
      Depending on the device, interrupts acknowledgement is done by setting
      or by clearing a dedicated register. Replace irq_gc_ack() with some
      {set,clr}_bit variants allows to handle both cases.
      
      Note that this patch affects the following SoCs: Davinci, Samsung and
      Orion. Except for this last, the change is minor: irq_gc_ack() is just
      renamed into irq_gc_ack_set_bit().
      
      For the Orion SoCs, the edge GPIO interrupts support is currently
      broken. irq_gc_ack() try to acknowledge a such interrupt by setting
      the corresponding cause register bit. The Orion GPIO device expect the
      opposite. To fix this issue, the irq_gc_ack_clr_bit() variant is used.
      
      Tested on Network Space v2.
      Reported-by: NJoey Oravec <joravec@drewtech.com>
      Signed-off-by: NSimon Guinot <sguinot@lacie.com>
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      659fb32d
  4. 24 5月, 2011 1 次提交
  5. 17 5月, 2011 13 次提交
  6. 29 3月, 2011 4 次提交
  7. 04 3月, 2011 2 次提交
  8. 14 1月, 2011 1 次提交
  9. 23 12月, 2010 3 次提交
  10. 22 10月, 2010 1 次提交
    • N
      [ARM] Kirkwood: restrict the scope of the PCIe reset workaround · 3924996b
      Nicolas Pitre 提交于
      Commit 21f0ba90 "orion/kirkwood: reset PCIe unit on boot" made the
      reset of the PCIe unit unconditional.  While this may fix problems on some
      targets, this also causes problems on other targets.
      
      Saeed Bishara <saeed@marvell.com> said about the original problem: "We
      couln't pinpoint the root cause of this issue, actually we failed to
      reproduce that issue."
      
      So let's restrict the reset of the PCIe unit only to the target where
      the original problem was observed.
      Signed-off-by: NNicolas Pitre <nico@fluxnic.net>
      3924996b
  11. 17 7月, 2010 1 次提交
  12. 31 5月, 2010 1 次提交
  13. 14 5月, 2010 1 次提交
  14. 29 12月, 2009 1 次提交
  15. 24 8月, 2009 1 次提交
    • M
      [ARM] Kirkwood: __init requires linux/init.h · 3e475f57
      Martin Michlmayr 提交于
      Include linux/init.h for __init to fix this error:
      
      CC [M]  drivers/net/wireless/wl12xx/boot.o
      In file included from arch/arm/mach-kirkwood/include/mach/gpio.h:13,
                       from arch/arm/include/asm/gpio.h:5,
                       from include/linux/gpio.h:7,
                       from drivers/net/wireless/wl12xx/boot.c:24:
      arch/arm/plat-orion/include/plat/gpio.h:32: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘orion_gpio_init’
      make[6]: *** [drivers/net/wireless/wl12xx/boot.o] Error 1
      make[5]: *** [drivers/net/wireless/wl12xx] Error 2
      Signed-off-by: NMartin Michlmayr <tbm@cyrius.com>
      Signed-off-by: NNicolas Pitre <nico@marvell.com>
      3e475f57
  16. 09 6月, 2009 4 次提交
  17. 24 4月, 2009 1 次提交
    • N
      [ARM] 5460/1: Orion: reduce namespace pollution · fdd8b079
      Nicolas Pitre 提交于
      Symbols like SOFT_RESET are way too generic to be exported at large.
      To avoid this, let's move the mbus bridge register defines into a
      separate file and include it where needed.  This affects mach-kirkwood,
      mach-loki, mach-mv78xx0 and mach-orion5x simultaneously as they all
      share code in plat-orion which relies on those defines.
      
      Some other defines have been moved to narrower scopes, or simply deleted
      when they had no user.
      
      This fixes compilation problem with mpt2sas on the above listed
      platforms.
      Signed-off-by: NNicolas Pitre <nico@marvell.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      fdd8b079