1. 04 2月, 2014 2 次提交
  2. 10 12月, 2013 5 次提交
  3. 24 11月, 2013 2 次提交
  4. 08 10月, 2013 2 次提交
  5. 30 9月, 2013 5 次提交
  6. 22 9月, 2013 1 次提交
    • S
      ARM: shmobile: Lager: add Micrel KSZ8041 PHY fixup · 48c8b96f
      Sergei Shtylyov 提交于
      Currently on the Lager board NFS timeouts/delays are seen when booting.  That
      turned out to happen because the SoC's ETH_LINK signal turns on and off after
      each packet.  It is connected to Micrel KSZ8041 PHY's LED0 signal. Ether LEDs
      on the Lager board are named LINK and ACTIVE which corresponds to non-default
      01 setting of the PHY control register 1 bits 14-15. The 'sh_eth' driver resets
      the PHY when opening the network device, so we have to set the mentioned bits
      back to 01 from the default 00 value which causes bouncing of ETH_LINK.  That
      can be achieved using the PHY platform fixup mechanism if we also modify the
      driver to use it..
      Signed-off-by: NSergei Shtylyov <sergei.shtylyov@cogentembedded.com>
      Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      48c8b96f
  7. 20 9月, 2013 1 次提交
  8. 10 9月, 2013 1 次提交
  9. 06 8月, 2013 2 次提交
  10. 31 7月, 2013 1 次提交
    • S
      ARM: shmobile: lager: do not annotate gpio_buttons as __initdata · a6014693
      Simon Horman 提交于
      When the gpio-keys device is registered using
      platform_device_register_data() the platform data argument,
      lager_keys_pdata is duplicated and thus should be marked as __initdata
      to avoid wasting memory. However, this is not true of gpio_buttons,
      a reference to it rather than its value is duplicated when lager_keys_pdata
      is duplicated.
      
      This avoids accessing freed memory if gpio-key events occur
      after unused kernel memory is freed late in the kernel's boot.
      
      This but was added when support for gpio-keys was added to lager
      in c3842e4f
      ("ARM: shmobile: lager: support GPIO switches") which was included
      in v3.11-rc1.
      Tested-by: NMagnus Damm <damm@opensource.se>
      Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      a6014693
  11. 17 7月, 2013 3 次提交
  12. 07 6月, 2013 2 次提交
  13. 05 6月, 2013 1 次提交
  14. 09 4月, 2013 1 次提交
  15. 03 4月, 2013 2 次提交
  16. 02 4月, 2013 1 次提交
  17. 19 4月, 2012 1 次提交
  18. 15 3月, 2012 1 次提交
  19. 10 3月, 2012 1 次提交
  20. 22 2月, 2012 1 次提交
  21. 16 11月, 2011 1 次提交
  22. 23 10月, 2011 1 次提交
    • M
      ARM: gic: consolidate PPI handling · 292b293c
      Marc Zyngier 提交于
      PPI handling is a bit of an odd beast. It uses its own low level
      handling code and is hardwired to the local timers (hence lacking
      a registration interface).
      
      Instead, switch the low handling to the normal SPI handling code.
      PPIs are handled by the handle_percpu_devid_irq flow.
      
      This also allows the removal of some duplicated code.
      
      Cc: Kukjin Kim <kgene.kim@samsung.com>
      Cc: David Brown <davidb@codeaurora.org>
      Cc: Bryan Huntsman <bryanh@codeaurora.org>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Paul Mundt <lethal@linux-sh.org>
      Cc: Magnus Damm <magnus.damm@gmail.com>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Acked-by: NDavid Brown <davidb@codeaurora.org>
      Tested-by: NDavid Brown <davidb@codeaurora.org>
      Tested-by: NShawn Guo <shawn.guo@linaro.org>
      Signed-off-by: NMarc Zyngier <marc.zyngier@arm.com>
      292b293c
  23. 07 1月, 2011 1 次提交
  24. 17 12月, 2010 1 次提交
    • M
      ARM: mach-shmobile: INTC interrupt priority level demux fix · 1cf215a5
      Magnus Damm 提交于
      Fix interrupt priority level handling on SH-Mobile ARM.
      
      SH-Mobile ARM platforms using multiple interrupt priority
      levels need this patch to fix a potential dead lock that
      may occur if multiple interrupts with different levels
      are pending simultaneously.
      
      The default INTC configuration is to use the same priority
      level for all interrupts, so this issue does not trigger by
      default. It is however common for board code to override the
      interrupt priority for certain interrupt sources depending
      on the application. Without this fix such boards may lock up.
      
      In detail, this patch updates the INTC code in entry-macro.S
      to make sure that the INTLVLA register gets set as expected.
      
      To trigger this bug modify the board specific code to adjust
      the interrupt priority level for the ethernet chip. After
      changing the priority level simply use flood ping to drown
      the board with interrupts.
      
      This patch applies to INTCA-based processors such as sh7372,
      sh7377 and sh7372. GIC-based processors are not affected.
      
      Suitable for v2.6.37-rc and stable from v2.6.34 to v2.6.36.
      
      Cc: stable@kernel.org
      Signed-off-by: NMagnus Damm <damm@opensource.se>
      Tested-by: NKuninori Morimoto <kuninori.morimoto.gx@renesas.com>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      1cf215a5