04.06.2019 14:20, Thierry Reding пишет: > On Thu, May 02, 2019 at 02:38:13AM +0300, Dmitry Osipenko wrote: >> The driver's compilation doesn't have any specific dependencies, hence >> the COMPILE_TEST option can be supported in Kconfig. >> >> Reviewed-by: Chanwoo Choi <cw00.choi@xxxxxxxxxxx> >> Signed-off-by: Dmitry Osipenko <digetx@xxxxxxxxx> >> --- >> drivers/devfreq/Kconfig | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/drivers/devfreq/Kconfig b/drivers/devfreq/Kconfig >> index 56db9dc05edb..a6bba6e1e7d9 100644 >> --- a/drivers/devfreq/Kconfig >> +++ b/drivers/devfreq/Kconfig >> @@ -93,7 +93,7 @@ config ARM_EXYNOS_BUS_DEVFREQ >> >> config ARM_TEGRA_DEVFREQ >> tristate "NVIDIA Tegra30/114/124/210 DEVFREQ Driver" >> - depends on ARCH_TEGRA >> + depends on ARCH_TEGRA || COMPILE_TEST >> select PM_OPP >> help >> This adds the DEVFREQ driver for the Tegra family of SoCs. > > You need to be careful with these. You're using I/O register accessors, > which are not supported on the UM architecture, for example. > > This may end up getting flagged during build testing. We have similar cases in other drivers and it doesn't cause any known problems because (I think) build-bots are aware of this detail. Hence there is no real need to be overreactive here and in this particular case it's better to react to real problems once they show up (we already did that by fixing build breakage caused by a CLK API problem found by bot in v3). Does it sound like a good argument to you? ACK?
