Hi Huacai On Fri, Nov 17, 2017 at 12:37:30PM +0800, Huacai Chen wrote: > I think it is better to make LOONGSON1_CPUFREQ depends on > CPU_LOONGSON1, and LOONGSON2_CPUFREQ depends on CPU_LOONGSON2 Yes, that may well be preferable, however as stated below both drivers have stricter dependencies than that which break the build for certain configurations: > On Thu, Nov 16, 2017 at 5:17 AM, James Hogan wrote: > > More specifically loongson1-cpufreq.c uses RST_CPU_EN and RST_CPU, > > neither of which is defined in asm/mach-loongson32/regs-clk.h unless > > CONFIG_LOONGSON1_LS1B=y, and loongson2_cpufreq.c references > > loongson2_clockmod_table[], which is only defined in > > arch/mips/loongson64/lemote-2f/clock.c, i.e. when > > CONFIG_LEMOTE_MACH2F=y. If those issues are fixed such that the drivers build on any respective loongson1 / loongson2 configuration then the dependencies can always be updated again to reflect that. Cheers James