summaryrefslogtreecommitdiff
path: root/scripts/rt-tester/t5-l4-pi-boost-deboost.tst
diff options
context:
space:
mode:
authorGeert Uytterhoeven <geert+renesas@glider.be>2014-05-06 23:26:19 +0200
committerSimon Horman <horms+renesas@verge.net.au>2014-05-12 16:05:01 +0900
commit3c90c55dcde745bed81f6447f24ba96bda43d984 (patch)
treea4498bea0f364e03247627e5259900f60e78243e /scripts/rt-tester/t5-l4-pi-boost-deboost.tst
parentc9eaa447e77efe77b7fa4c953bd62de8297fd6c5 (diff)
drivers: sh: compile drivers/sh/pm_runtime.c if ARCH_SHMOBILE_MULTI
If the kernel is built to support multi-ARM configuration with shmobile support built in, then drivers/sh is not built. This contains the PM runtime code in drivers/sh/pm_runtime.c, which implicitly enables the module clocks for all devices, and thus is quite essential. Without this, the state of clocks depends on implicit reset state, or on the bootloader. If ARCH_SHMOBILE_MULTI then build the drivers/sh directory, but ensure that bits that may conflict (drivers/sh/clk if the common clock framework is enabled) or are not used (drivers/sh/intc), are not built. Also, only enable the PM runtime code when actually running on a shmobile SoCs that needs it. ARCH_SHMOBILE_MULTI was added a while ago by commit efacfce5f8a523457e9419a25d52fe39db00b26a ("ARM: shmobile: Introduce ARCH_SHMOBILE_MULTI"), but drivers/sh was compiled for both ARCH_SHMOBILE_LEGACY and ARCH_SHMOBILE_MULTI until commit bf98c1eac1d4a6bcf00532e4fa41d8126cd6c187 ("ARM: Rename ARCH_SHMOBILE to ARCH_SHMOBILE_LEGACY"). Inspired by a patch from Ben Dooks <ben.dooks@codethink.co.uk>. Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
Diffstat (limited to 'scripts/rt-tester/t5-l4-pi-boost-deboost.tst')
0 files changed, 0 insertions, 0 deletions