On 07/02/2021 04:31, Guo Ren wrote: > Hi Daniel, > > On Thu, Feb 4, 2021 at 4:48 PM Daniel Lezcano <daniel.lezc...@linaro.org> > wrote: >> >> On 04/02/2021 08:46, guo...@kernel.org wrote: >>> From: Guo Ren <guo...@linux.alibaba.com> >>> >>> The timer-mp-csky.c only could support CPU_CK860 and it will >>> compile error with CPU_CK610. >>> >>> It has been selected in arch/csky/Kconfig. >> >> It would be better if you fix the root cause of the compilation error. > The timer-mp-csky.c has used specific instructions which only > supported by CK860 and timer-mp-csky.c is only design for CK860.
I guess you are referring to mfcr() ? > In arch/csky/Konfig we only select it with CK860. > select CSKY_MPINTC if CPU_CK860 > select CSKY_MP_TIMER if CPU_CK860 > > So here let's select timer-mp-csky.c in arch/csky/Kconfig, not in > drivers/clocksource/Kconfig. The COMPILE_TEST option is there to let other architecture to compile drivers and increase the compilation test coverage. The proposed change just removes the driver from this coverage. Ideally, it would be better to keep it with the COMPILE_TEST option, so changes impacting all the drivers can be caught before submitting the patches. By just adding #ifndef mfcr #define mfcr(a) 0 #endif shoud fix the compilation issue, no ? -- <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook | <http://twitter.com/#!/linaroorg> Twitter | <http://www.linaro.org/linaro-blog/> Blog
