1. 19 7月, 2014 1 次提交
  2. 11 7月, 2014 2 次提交
  3. 08 7月, 2014 1 次提交
  4. 05 7月, 2014 1 次提交
  5. 21 6月, 2014 1 次提交
    • D
      ARM: EXYNOS: Don't rely on firmware's secondary_cpu_start for mcpm · 7cbcb9d4
      Doug Anderson 提交于
      On exynos mcpm systems the firmware is hardcoded to jump to an address
      in SRAM (0x02073000) when secondary CPUs come up.  By default the
      firmware puts a bunch of code at that location.  That code expects the
      kernel to fill in a few slots with addresses that it uses to jump back
      to the kernel's entry point for secondary CPUs.
      
      Originally (on prerelease hardware) this firmware code contained a
      bunch of workarounds to deal with boot ROM bugs.  However on all
      shipped hardware we simply use this code to redirect to a kernel
      function for bringing up the CPUs.
      
      Let's stop relying on the code provided by the bootloader and just
      plumb in our own (simple) code jump to the kernel.  This has the nice
      benefit of fixing problems due to the fact that older bootloaders
      (like the one shipped on the Samsung Chromebook 2) might have put
      slightly different code into this location.
      
      Once suspend/resume is implemented for systems using exynos-mcpm we'll
      need to make sure we reinstall our fixed up code after resume.  ...but
      that's not anything new since IRAM (and thus the address of the
      mcpm_entry_point) is lost across suspend/resume anyway.
      Signed-off-by: NDoug Anderson <dianders@chromium.org>
      Acked-by: NKevin Hilman <khilman@linaro.org>
      Tested-by: NKevin Hilman <khilman@linaro.org>
      Acked-by: NNicolas Pitre <nico@linaro.org>
      Signed-off-by: NKukjin Kim <kgene.kim@samsung.com>
      7cbcb9d4
  6. 18 6月, 2014 1 次提交
    • A
      ARM: EXYNOS: fix pm code to check for cortex A9 rather than the SoC · c0c3c359
      Abhilash Kesavan 提交于
      We have an soc check to ensure that the scu and certain A9 specific
      registers are not accessed on Exynos5250 (which is A15 based).
      Rather than adding another soc specific check for 5420 let us test
      for the Cortex A9 primary part number.
      
      This resolves the below crash seen on exynos5420 during core switching
      after the CPUIdle consolidation series was merged.
      
      [  155.975589] [<c0013174>] (scu_enable) from [<c001b0dc>] (exynos_cpu_pm_notifier+0x80/0xc4)
      [  155.983833] [<c001b0dc>] (exynos_cpu_pm_notifier) from [<c003c1b0>] (notifier_call_chain+0x44/0x84)
      [  155.992851] [<c003c1b0>] (notifier_call_chain) from [<c007a49c>] (cpu_pm_notify+0x20/0x3c)
      [  156.001089] [<c007a49c>] (cpu_pm_notify) from [<c007a564>] (cpu_pm_exit+0x20/0x38)
      [  156.008635] [<c007a564>] (cpu_pm_exit) from [<c0019e98>] (bL_switcher_thread+0x298/0x40c)
      [  156.016788] [<c0019e98>] (bL_switcher_thread) from [<c003842c>] (kthread+0xcc/0xe8)
      [  156.024426] [<c003842c>] (kthread) from [<c000e438>] (ret_from_fork+0x14/0x3c)
      [  156.031621] Code: ea017fec c0530a00 c052e3f8 c0012dcc (e5903000
      Signed-off-by: NAbhilash Kesavan <a.kesavan@samsung.com>
      Signed-off-by: NKukjin Kim <kgene.kim@samsung.com>
      c0c3c359
  7. 17 6月, 2014 4 次提交
  8. 16 6月, 2014 1 次提交
  9. 01 6月, 2014 1 次提交
  10. 31 5月, 2014 10 次提交
  11. 30 5月, 2014 5 次提交
  12. 26 5月, 2014 12 次提交