On 25/07/2025 11:03, Krzysztof Kozlowski wrote:
Commit 5d86e479193b ("clocksource/drivers/exynos_mct: Add module
support") introduced section mismatch failures.
Commit 7e477e9c4eb4 ("clocksource/drivers/exynos_mct: Fix section
mismatch from the module conversion") replaced these to other section
mismatch failures:
WARNING: modpost: vmlinux: section mismatch in reference: mct_init_dt+0x164 (section: .text) -> register_current_timer_delay (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: mct_init_dt+0x20c (section: .text) -> register_current_timer_delay (section: .init.text)
ERROR: modpost: Section mismatches detected.
No progress on real fixing of these happened (intermediary fix was still
not tested), so revert both commits till the work is prepared correctly.
Please don't claim the fix was not tested. I reproduced the section
mismatch, tested it and figured out it was indeed fixing the issue. I
just missed the error because it sounds very close to the first one
reported initially and I did the confusion.
The driver is not supposed to be compiled as a module on ARM32.
The option tristate "Exynos multi core timer driver" if ARM64 is
misleading. From this change, the defconfig on ARM can do
CONFIG_EXYNOS_MCT=m which should not be allowed.
Before getting wild and revert everything, let's try to find a proper
fix for that.
Thanks
--
<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
