1. 17 8月, 2017 1 次提交
  2. 28 2月, 2017 1 次提交
  3. 12 4月, 2016 1 次提交
  4. 17 12月, 2015 1 次提交
  5. 02 12月, 2015 1 次提交
  6. 19 11月, 2015 1 次提交
  7. 06 7月, 2015 4 次提交
    • C
      ARM: rockchip: fix broken build · cb8cc37f
      Caesar Wang 提交于
      The following was seen in branch[0] build.
      
      arch/arm/mach-rockchip/platsmp.c:154:23: error:
          'rockchip_secondary_startup' undeclared (first use in this function)
      
      branch[0]:
      git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git
      v4.3-armsoc/soc
      
      The broken build is caused by the commit fe4407c0
      ("ARM: rockchip: fix the CPU soft reset").
      Signed-off-by: NCaesar Wang <wxt@rock-chips.com>
      
      The breakage was a result of it being wrongly merged in my branch with
      the cache invalidation rework from Russell 02b4e275
      ("ARM: v7 setup function should invalidate L1 cache").
      Signed-off-by: NHeiko Stuebner <heiko@sntech.de>
      cb8cc37f
    • C
      ARM: rockchip: fix the SMP code style · 7f0b61ad
      Caesar Wang 提交于
      Use the below scripts to check:
      scripts/checkpatch.pl -f --subject arch/arm/mach-rockchip/platsmp.c
      Signed-off-by: NCaesar Wang <wxt@rock-chips.com>
      Reviewed-by: NDouglas Anderson <dianders@chromium.org>
      Reviewed-by: NKever Yang <kever.yang@rock-chips.com>
      Signed-off-by: NHeiko Stuebner <heiko@sntech.de>
      7f0b61ad
    • C
      ARM: rockchip: ensure CPU to enter WFI/WFE state · e306bc16
      Caesar Wang 提交于
      The patch can ensure that v7_exit_coherency_flush() in rockchip_cpu_die()
      executed in time.
      The mdelay(1) has enough time to fix the problem of CPU offlining.
      That's a workaround way in rockchip hotplug code,
      At least, we haven't a better way to solve it. Who know,
      that maybe fixed by chip (hardware) in the future.
      Signed-off-by: NCaesar Wang <wxt@rock-chips.com>
      Reviewed-by: NDouglas Anderson <dianders@chromium.org>
      Reviewed-by: NKever Yang <kever.yang@rock-chips.com>
      Signed-off-by: NHeiko Stuebner <heiko@sntech.de>
      e306bc16
    • C
      ARM: rockchip: fix the CPU soft reset · fe4407c0
      Caesar Wang 提交于
      We need different orderings when turning a core on and turning a core
      off.  In one case we need to assert reset before turning power off.
      In ther other case we need to turn power on and the deassert reset.
      
      In general, the correct flow is:
      
      CPU off:
          reset_control_assert
          regmap_update_bits(pmu, PMU_PWRDN_CON, BIT(pd), BIT(pd))
          wait_for_power_domain_to_turn_off
      CPU on:
          regmap_update_bits(pmu, PMU_PWRDN_CON, BIT(pd), 0)
          wait_for_power_domain_to_turn_on
          reset_control_deassert
      
      This is needed for stressing CPU up/down, as per:
          cd /sys/devices/system/cpu/
          for i in $(seq 10000); do
              echo "================= $i ============"
              for j in $(seq 100); do
                  while [[ "$(cat cpu1/online)$(cat cpu2/online)$(cat cpu3/online)" != "000"" ]]
                      echo 0 > cpu1/online
                      echo 0 > cpu2/online
                      echo 0 > cpu3/online
                  done
                  while [[ "$(cat cpu1/online)$(cat cpu2/online)$(cat cpu3/online)" != "111" ]]; do
                      echo 1 > cpu1/online
                      echo 1 > cpu2/online
                      echo 1 > cpu3/online
                  done
              done
          done
      
      The following is reproducable log:
          [34466.186812] PM: noirq suspend of devices complete after 0.669 msecs
          [34466.186824] Disabling non-boot CPUs ...
          [34466.187509] CPU1: shutdown
          [34466.188672] CPU2: shutdown
          [34473.736627] Kernel panic - not syncing:Watchdog detected hard LOCKUP on cpu 0
          .......
      or others similar log:
          .......
          [ 4072.454453] CPU1: shutdown
          [ 4072.504436] CPU2: shutdown
          [ 4072.554426] CPU3: shutdown
          [ 4072.577827] CPU1: Booted secondary processor
          [ 4072.582611] CPU2: Booted secondary processor
          <hang>
      
          Tested by cpu up/down scripts, the results told us need delay more time
      before write the sram. The wait time is affected by many aspects
      (e.g: cpu frequency, bootrom frequency, sram frequency, bus speed, ...).
      
          Although the cpus other than cpu0 will write the sram, the speedy is
      no the same as cpu0, if the cpu0 early wake up, perhaps the other cpus
      can't startup. As we know, the cpu0 can wake up when the cpu1/2/3 write
      the 'sram+4/8' and send the sev.
          Anyway.....
          At the moment, 1ms delay will be happy work for cpu up/down scripts test.
      Signed-off-by: NCaesar Wang <wxt@rock-chips.com>
      Reviewed-by: NDoug Anderson <dianders@chromium.org>
      Reviewed-by: NKever Yang <kever.yang@rock-chips.com>
      Fixes: 3ee851e2 ("ARM: rockchip: add basic smp support for rk3288")
      Cc: stable@vger.kernel.org
      Signed-off-by: NHeiko Stuebner <heiko@sntech.de>
      fe4407c0
  8. 17 6月, 2015 1 次提交
  9. 01 6月, 2015 1 次提交
  10. 12 3月, 2015 1 次提交
  11. 06 11月, 2014 3 次提交
  12. 23 7月, 2014 1 次提交
  13. 27 5月, 2014 1 次提交
  14. 15 4月, 2014 1 次提交
  15. 02 3月, 2014 1 次提交