Messages in this thread | | | Date | Wed, 15 Feb 2023 14:46:27 +0000 | From | Sudeep Holla <> | Subject | Re: [PATCH v2 4/4] clocksource/drivers/timer-mediatek: Make timer-mediatek become loadable module |
| |
On Wed, Feb 15, 2023 at 02:30:51PM +0100, AngeloGioacchino Del Regno wrote: > > Both. I mean that these platforms do have architected timers, but they are stopped > before the bootloader jumps to the kernel, or they are never started at all. > > Please refer to: > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/clocksource/timer-mediatek.c?h=next-20230215&id=327e93cf9a59b0d04eb3a31a7fdbf0f11cf13ecb > > For a nice explanation. >
Thanks for that. Well then I see no point in making these modules if you can't have generic Image that boots on all the platform. I now tend to think that these are made modules just because GKI demands and it *might* work on one or 2 platforms. One we move this as modules, how will be know the Image without these timers or with them built as modules will boot or not on a given mediatek platform. Sorry, I initially saw some point in making these timers as modules but if they are required for boot on some systems then I see no point. So if that is the case, NACK for these as it just creates more confusion after these are merged as why some Images or even why defconfig image(if we push the config change as well) is not booting on these platforms.
It is no longer just for system timer useful in low power CPU idle states as I initial thought.
-- Regards, Sudeep
| |