Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
接近 2 年 前同步成功

通知 170
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 03 6月, 2015 13 次提交
  3. 29 5月, 2015 1 次提交
  5. 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
  7. 23 5月, 2015 2 次提交
  9. 22 5月, 2015 1 次提交
  11. 21 5月, 2015 3 次提交
  13. 19 5月, 2015 2 次提交
  15. 18 5月, 2015 1 次提交
  17. 17 5月, 2015 10 次提交
  19. 15 5月, 2015 1 次提交
    • R
      ARM: fix missing syscall trace exit · 1b979372
      由 Russell King 提交于 
      Josh Stone reports:

  I've discovered a case where both arm and arm64 will miss a ptrace
  syscall-exit that they should report.  If the syscall is entered
  without TIF_SYSCALL_TRACE set, then it goes on the fast path.  It's
  then possible to have TIF_SYSCALL_TRACE added in the middle of the
  syscall, but ret_fast_syscall doesn't check this flag again.

Fix this by always checking for a syscall trace in the fast exit path.
Reported-by: NJosh Stone <jistone@redhat.com>
Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      1b979372
  21. 14 5月, 2015 4 次提交