summaryrefslogtreecommitdiffstats
path: root/arch/cris
diff options
context:
space:
mode:
authorSean Wang <sean.wang@mediatek.com>2018-01-05 16:14:06 +0800
committerStephen Boyd <sboyd@codeaurora.org>2018-01-10 13:41:15 -0800
commitbc27360b3c7aedfc385f7fc0527a42918bdeba51 (patch)
treef28f2a392dd7f9ff425b3e9de009baa92fbd3421 /arch/cris
parent5589818b2fab09c4b7250865a6163c3e2f81a9d6 (diff)
downloadlinux-bc27360b3c7aedfc385f7fc0527a42918bdeba51.tar.bz2
clk: mediatek: adjust dependency of reset.c to avoid unexpectedly being built
Changes from v1->v2: Add 'select RESET_CONTROLLER' under COMMON_CLK_MEDIATEK and enable reset.c to be built when COMMON_CLK_MEDIATEK is selected. That should be quite reasonable because the reset controller is tightly embedded inside and exported from these clock subsystems. At least it can be found on infracfg and pericfg subsystem that both are really fundamental block lots of devices must depend on. commit 74cb0d6dde8 ("clk: mediatek: fixup test-building of MediaTek clock drivers") can let the build system looking into the directory where the clock drivers resides and then allow test-building the drivers. But the change also gives rise to certain incorrect behavior which is reset.c being built even not depending on either COMPILE_TEST or ARCH_MEDIATEK alternative dependency. To get rid of reset.c being built unexpectedly on the other platforms, it would be a good change that the file should be built depending on its own specific configuration rather than just on generic RESET_CONTROLLER one. Signed-off-by: Sean Wang <sean.wang@mediatek.com> Cc: Jean Delvare <jdelvare@suse.de> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Diffstat (limited to 'arch/cris')
0 files changed, 0 insertions, 0 deletions