summaryrefslogtreecommitdiffstats
path: root/drivers/clocksource/Kconfig
diff options
context:
space:
mode:
Diffstat (limited to 'drivers/clocksource/Kconfig')
-rw-r--r--drivers/clocksource/Kconfig27
1 files changed, 10 insertions, 17 deletions
diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
index fc5a389b95..598edc9a81 100644
--- a/drivers/clocksource/Kconfig
+++ b/drivers/clocksource/Kconfig
@@ -18,28 +18,21 @@ config CLOCKSOURCE_DIGIC
bool
depends on ARCH_DIGIC
-config CLOCKSOURCE_DUMMY
- bool "Enable dummy software-only clocksource"
+config CLOCKSOURCE_DUMMY_RATE
+ int
+ prompt "dummy clocksource rate"
+ default 1000
help
When porting barebox to a new SoC there might be a case
of broken or absent clocksource. This causes barebox serial
console to be non functional.
- To solve the problem this software-only clocksource driver is used.
- WARNING!!! This clocksource doesn't provide correct timing.
- To adjust this clocksource please use CONFIG_CLOCKSOURCE_DUMMY_RATE.
+ To solve the problem barebox has built-in software-only clocksource.
+ The software-only clocksource is used only if no hardware clocksource
+ is registered. This can help if initialization order is wrong so that
+ the time functions are used before the real clocksource was initialized.
+ WARNING!!! Built-in software-only clocksource doesn't provide correct timing.
+ The option CONFIG_CLOCKSOURCE_DUMMY_RATE is used to adjust this clocksource.
The bigger rate valuest makes clocksource "faster".
- It's possible to add this clocksource unconditionally.
- This clocksource starts very early (pure_initcall) so
- real clocksource will take over.
- This can help if initialization order is wrong so that
- the time functions are used before the real clocksource
- was initialized.
-
-config CLOCKSOURCE_DUMMY_RATE
- int
- prompt "dummy clocksource rate"
- depends on CLOCKSOURCE_DUMMY
- default 1000
config CLOCKSOURCE_MVEBU
bool