1. 03 6月, 2015 32 次提交
  2. 01 6月, 2015 1 次提交
  3. 27 5月, 2015 2 次提交
    • L
      ARM: imx6: gpc: don't register power domain if DT data is missing · b17c70cd
      Lucas Stach 提交于
      If the devicetree is too old and does not provide the regulator and clocks
      for the power domain, we need to avoid registering the power domain.
      Otherwise runtime PM will try to control the domain, which will lead to
      machine hangs without the proper DT configuration data.
      
      This restores functionality to the kernel 4.0 level if an old DT is
      detected, where the power domain is constantly powered on.
      Signed-off-by: NLucas Stach <l.stach@pengutronix.de>
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      b17c70cd
    • L
      ARM: imx6: allow booting with old DT · 634a6037
      Lucas Stach 提交于
      The GPC rewrite to IRQ domains has been on the premise that it may break
      suspend/resume for new kernels on old DT, but otherwise keep things working
      from a user perspective. This was an accepted compromise to be able to move
      the GIC cleanup forward.
      
      What actually happened was that booting a new kernel on an old DT crashes
      before even the console is up, so the user does not even see the warning
      that the DT is too old. The warning message suggests that this has been
      known before, which is clearly unacceptable.
      
      Fix the early crash by mapping the GPC memory space if the IRQ controller
      doesn't claim it. This keeps at least CPUidle and the needed CPU wakeup
      workarounds working. With this fixed the system is able to boot up
      properly minus the expected suspend/resume breakage.
      Signed-off-by: NLucas Stach <l.stach@pengutronix.de>
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      634a6037
  4. 21 5月, 2015 1 次提交
    • S
      ARM: vf610: enable Cortex-M4 configuration on Vybrid SoC · 8064887e
      Stefan Agner 提交于
      This patch allows to build the Kernel for Vybrid (VF6xx) SoC
      when ARMv7-M CPU is selected. The resulting image runs on the
      secondary Cortex-M4 core. This core has equally access to all
      peripherals as the main Cortex-A5 core. However, there is no
      resource control mechanism, hence when both cores are used
      simultaneously, orthogonal device tree's are required.
      
      The boot CPU is dependent on the SoC variant. The available
      boards use mostly variants where the Cortex-A5 is the primary
      and hence the boot CPU. Booting the secondary Cortex-M4 CPU
      needs SoC specific registers written. There is no in kernel
      support for this right now, a external userspace utility
      called "m4boot" can be used to boot the kernel:
      
      m4boot xipImage initramfs.cpio.lzo vf610m4-colibri.dtb
      Signed-off-by: NStefan Agner <stefan@agner.ch>
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      8064887e
  5. 14 5月, 2015 1 次提交
  6. 11 5月, 2015 2 次提交
  7. 27 4月, 2015 1 次提交