1. 10 7月, 2013 1 次提交
  2. 12 1月, 2013 1 次提交
    • T
      ARM: OMAP2+: Use omap initcalls · b76c8b19
      Tony Lindgren 提交于
      This way the initcalls don't run on other SoCs on multiplatform
      kernels. Otherwise we'll get something like this when booting
      on vexpress:
      
      omap_hwmod: _ensure_mpu_hwmod_is_setup: MPU initiator hwmod mpu not yet registered
      ...
      WARNING: at arch/arm/mach-omap2/pm.c:82 _init_omap_device+0x74/0x94()
      _init_omap_device: could not find omap_hwmod for mpu
      ...
      omap-dma-engine omap-dma-engine: OMAP DMA engine driver
      ...
      Tested-by: NEzequiel Garcia <ezequiel.garcia@free-electrons.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      b76c8b19
  3. 09 11月, 2012 1 次提交
    • P
      ARM: OMAP2+: PRCM: create SoC-specific chip restart functions · 2f334a38
      Paul Walmsley 提交于
      Split omap_prcm_restart() from mach-omap2/prcm.c into SoC-specific
      variants.  These functions need to be able to save the reboot reason
      into the scratchpad RAM.  This implies a dependency on both the PRM
      and SCM IP blocks, so they've been moved into their own file.  This
      will eventually call functions in the PRM and SCM drivers, once those
      are created.
      
      Vaibhav Hiremath <hvaibhav@ti.com> identified an unused prototype in
      the first version of this patch - now removed.  Tony Lindgren
      <tony@atomide.com> noted a compile problem with some RMK Kconfigs;
      resolved in this patch.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Cc: Vaibhav Hiremath <hvaibhav@ti.com>
      Tested-by: NVaibhav Hiremath <hvaibhav@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      2f334a38