2014-06-16 03:48:45 -06:00
|
|
|
menu "Clock Source drivers"
|
clocksource: Improve GENERIC_CLOCKEVENTS dependency
We regularly run into build errors when a clocksource driver selects
CONFIG_TIMER_OF while CONFIG_GENERIC_CLOCKEVENTS is disabled:
In file included from drivers/clocksource/timer-of.c:25:0:
drivers/clocksource/timer-of.h:35:28: error: field 'clkevt' has incomplete type
At the moment, three drivers can show this behavior: ARMV7M_SYSTICK,
CLKSRC_ST_LPC and CLKSRC_NPS. We could add further dependencies as we did
many times, but I have looked a little bit more at what architectures
are left that don't use GENERIC_CLOCKEVENTS, and this shows that there
is a better solution.
On arch/frv and arch/ia64, we never select CONFIG_GENERIC_CLOCKEVENTS
and we also don't use ARCH_USES_GETTIMEOFFSET, which would
block the clocksource Kconfig menu. On m68k, some platforms use
CONFIG_GENERIC_CLOCKEVENTS, some use ARCH_USES_GETTIMEOFFSET, and some
use neither of them. The good news is that there is no configuration that
does not set CONFIG_GENERIC_CLOCKEVENTS but that wants to enable any of
the Kconfig symbols in the menu, so we can simply replace the dependency
with the stricter one. While in theory one could have a clocksource
driver without the clockevent infrastructure, this seems unlikely
to be relevant in the future any more.
We can probably drop some of the other dependencies as well now,
e.g. there should generally be no reason to depend on CONFIG_ARM
unless the driver uses architecture specific assembly.
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
2017-09-05 09:04:56 -06:00
|
|
|
depends on GENERIC_CLOCKEVENTS
|
2014-06-16 03:48:45 -06:00
|
|
|
|
2017-05-26 11:34:11 -06:00
|
|
|
config TIMER_OF
|
2012-11-19 16:41:20 -07:00
|
|
|
bool
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_PROBE
|
2015-09-28 08:49:16 -06:00
|
|
|
|
2017-05-26 11:40:24 -06:00
|
|
|
config TIMER_ACPI
|
2015-09-28 08:49:16 -06:00
|
|
|
bool
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_PROBE
|
2015-09-28 08:49:16 -06:00
|
|
|
|
2017-05-26 11:34:11 -06:00
|
|
|
config TIMER_PROBE
|
2015-09-28 08:49:16 -06:00
|
|
|
bool
|
2012-11-19 16:41:20 -07:00
|
|
|
|
2011-05-08 11:47:58 -06:00
|
|
|
config CLKSRC_I8253
|
|
|
|
bool
|
2011-05-08 07:06:52 -06:00
|
|
|
|
2011-06-09 07:08:25 -06:00
|
|
|
config CLKEVT_I8253
|
|
|
|
bool
|
|
|
|
|
2011-06-01 12:04:59 -06:00
|
|
|
config I8253_LOCK
|
|
|
|
bool
|
|
|
|
|
2018-02-14 23:01:46 -07:00
|
|
|
config OMAP_DM_TIMER
|
|
|
|
bool
|
|
|
|
|
2011-06-01 12:04:59 -06:00
|
|
|
config CLKBLD_I8253
|
2011-06-09 07:08:25 -06:00
|
|
|
def_bool y if CLKSRC_I8253 || CLKEVT_I8253 || I8253_LOCK
|
2011-06-01 12:04:59 -06:00
|
|
|
|
2011-05-08 07:06:52 -06:00
|
|
|
config CLKSRC_MMIO
|
|
|
|
bool
|
2011-06-06 05:43:07 -06:00
|
|
|
|
2016-06-02 10:35:38 -06:00
|
|
|
config BCM2835_TIMER
|
|
|
|
bool "BCM2835 timer driver" if COMPILE_TEST
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
Enables the support for the BCM2835 timer driver.
|
|
|
|
|
2016-06-02 11:20:36 -06:00
|
|
|
config BCM_KONA_TIMER
|
|
|
|
bool "BCM mobile timer driver" if COMPILE_TEST
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
Enables the support for the BCM Kona mobile timer driver.
|
|
|
|
|
2015-01-26 11:35:18 -07:00
|
|
|
config DIGICOLOR_TIMER
|
2015-10-30 15:32:10 -06:00
|
|
|
bool "Digicolor timer driver" if COMPILE_TEST
|
2016-01-25 09:02:49 -07:00
|
|
|
select CLKSRC_MMIO
|
2016-01-25 15:24:19 -07:00
|
|
|
depends on HAS_IOMEM
|
2015-10-30 15:32:10 -06:00
|
|
|
help
|
|
|
|
Enables the support for the digicolor timer driver.
|
2015-01-26 11:35:18 -07:00
|
|
|
|
2011-06-06 05:43:07 -06:00
|
|
|
config DW_APB_TIMER
|
2015-10-30 15:35:00 -06:00
|
|
|
bool "DW APB timer driver" if COMPILE_TEST
|
|
|
|
help
|
|
|
|
Enables the support for the dw_apb timer.
|
2011-05-27 02:30:12 -06:00
|
|
|
|
2012-07-11 14:13:16 -06:00
|
|
|
config DW_APB_TIMER_OF
|
|
|
|
bool
|
2013-06-04 03:38:11 -06:00
|
|
|
select DW_APB_TIMER
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2012-07-11 14:13:16 -06:00
|
|
|
|
2017-03-24 15:32:34 -06:00
|
|
|
config FTTMR010_TIMER
|
|
|
|
bool "Faraday Technology timer driver" if COMPILE_TEST
|
2017-01-22 05:17:17 -07:00
|
|
|
depends on HAS_IOMEM
|
|
|
|
select CLKSRC_MMIO
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2017-01-22 05:17:17 -07:00
|
|
|
select MFD_SYSCON
|
|
|
|
help
|
2017-03-24 15:32:34 -06:00
|
|
|
Enables support for the Faraday Technology timer block
|
|
|
|
FTTMR010.
|
2017-01-22 05:17:17 -07:00
|
|
|
|
2015-01-25 14:06:02 -07:00
|
|
|
config ROCKCHIP_TIMER
|
2015-10-30 10:58:47 -06:00
|
|
|
bool "Rockchip timer driver" if COMPILE_TEST
|
|
|
|
depends on ARM || ARM64
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2017-01-31 05:43:14 -07:00
|
|
|
select CLKSRC_MMIO
|
2015-10-30 10:58:47 -06:00
|
|
|
help
|
|
|
|
Enables the support for the rockchip timer driver.
|
2015-01-25 14:06:02 -07:00
|
|
|
|
2012-06-13 10:58:09 -06:00
|
|
|
config ARMADA_370_XP_TIMER
|
2015-10-30 13:30:34 -06:00
|
|
|
bool "Armada 370 and XP timer driver" if COMPILE_TEST
|
|
|
|
depends on ARM
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2016-01-25 09:02:49 -07:00
|
|
|
select CLKSRC_MMIO
|
2015-10-30 13:30:34 -06:00
|
|
|
help
|
|
|
|
Enables the support for the Armada 370 and XP timer driver.
|
2012-06-13 10:58:09 -06:00
|
|
|
|
2014-09-28 17:50:05 -06:00
|
|
|
config MESON6_TIMER
|
2015-10-30 15:07:39 -06:00
|
|
|
bool "Meson6 timer driver" if COMPILE_TEST
|
2014-11-18 08:41:20 -07:00
|
|
|
select CLKSRC_MMIO
|
2015-10-30 15:07:39 -06:00
|
|
|
help
|
|
|
|
Enables the support for the Meson6 timer driver.
|
2014-09-28 17:50:05 -06:00
|
|
|
|
2013-06-11 00:38:50 -06:00
|
|
|
config ORION_TIMER
|
2015-10-30 15:28:31 -06:00
|
|
|
bool "Orion timer driver" if COMPILE_TEST
|
|
|
|
depends on ARM
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2013-06-11 00:38:50 -06:00
|
|
|
select CLKSRC_MMIO
|
2015-10-30 15:28:31 -06:00
|
|
|
help
|
|
|
|
Enables the support for the Orion timer driver
|
2013-06-11 00:38:50 -06:00
|
|
|
|
2017-02-23 11:27:12 -07:00
|
|
|
config OWL_TIMER
|
|
|
|
bool "Owl timer driver" if COMPILE_TEST
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
Enables the support for the Actions Semi Owl timer driver.
|
|
|
|
|
2018-12-10 10:35:46 -07:00
|
|
|
config RDA_TIMER
|
|
|
|
bool "RDA timer driver" if COMPILE_TEST
|
|
|
|
depends on GENERIC_CLOCKEVENTS
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
select TIMER_OF
|
|
|
|
help
|
|
|
|
Enables the support for the RDA Micro timer driver.
|
|
|
|
|
2013-03-24 04:49:25 -06:00
|
|
|
config SUN4I_TIMER
|
2015-10-30 15:39:00 -06:00
|
|
|
bool "Sun4i timer driver" if COMPILE_TEST
|
2016-01-25 15:24:19 -07:00
|
|
|
depends on HAS_IOMEM
|
2013-10-14 13:07:46 -06:00
|
|
|
select CLKSRC_MMIO
|
2017-06-06 15:07:51 -06:00
|
|
|
select TIMER_OF
|
2015-10-30 15:39:00 -06:00
|
|
|
help
|
|
|
|
Enables support for the Sun4i timer.
|
2012-11-12 07:07:50 -07:00
|
|
|
|
2013-11-07 04:01:48 -07:00
|
|
|
config SUN5I_HSTIMER
|
2015-10-31 10:01:46 -06:00
|
|
|
bool "Sun5i timer driver" if COMPILE_TEST
|
2013-11-07 04:01:48 -07:00
|
|
|
select CLKSRC_MMIO
|
2015-10-31 10:01:46 -06:00
|
|
|
depends on COMMON_CLK
|
|
|
|
help
|
|
|
|
Enables support the Sun5i timer.
|
2013-11-07 04:01:48 -07:00
|
|
|
|
2014-07-07 07:26:30 -06:00
|
|
|
config TEGRA_TIMER
|
2015-10-31 13:13:09 -06:00
|
|
|
bool "Tegra timer driver" if COMPILE_TEST
|
2016-01-25 09:02:49 -07:00
|
|
|
select CLKSRC_MMIO
|
2019-02-21 00:21:44 -07:00
|
|
|
select TIMER_OF
|
|
|
|
depends on ARM || ARM64
|
2015-10-31 13:13:09 -06:00
|
|
|
help
|
|
|
|
Enables support for the Tegra driver.
|
2014-07-07 07:26:30 -06:00
|
|
|
|
2013-01-13 21:58:21 -07:00
|
|
|
config VT8500_TIMER
|
2015-10-31 13:23:54 -06:00
|
|
|
bool "VT8500 timer driver" if COMPILE_TEST
|
2016-01-25 15:24:19 -07:00
|
|
|
depends on HAS_IOMEM
|
2015-10-31 13:23:54 -06:00
|
|
|
help
|
|
|
|
Enables support for the VT8500 driver.
|
2013-01-13 21:58:21 -07:00
|
|
|
|
2018-03-08 08:24:58 -07:00
|
|
|
config NPCM7XX_TIMER
|
|
|
|
bool "NPCM7xx timer driver" if COMPILE_TEST
|
|
|
|
depends on HAS_IOMEM
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
Enable 24-bit TIMER0 and TIMER1 counters in the NPCM7xx architecture,
|
|
|
|
While TIMER0 serves as clockevent and TIMER1 serves as clocksource.
|
|
|
|
|
2013-03-20 03:46:01 -06:00
|
|
|
config CADENCE_TTC_TIMER
|
2015-10-31 14:39:03 -06:00
|
|
|
bool "Cadence TTC timer driver" if COMPILE_TEST
|
|
|
|
depends on COMMON_CLK
|
|
|
|
help
|
|
|
|
Enables support for the cadence ttc driver.
|
2013-03-20 03:46:01 -06:00
|
|
|
|
2015-02-23 11:54:16 -07:00
|
|
|
config ASM9260_TIMER
|
2015-10-31 14:41:23 -06:00
|
|
|
bool "ASM9260 timer driver" if COMPILE_TEST
|
2015-02-23 11:54:16 -07:00
|
|
|
select CLKSRC_MMIO
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2015-10-31 14:41:23 -06:00
|
|
|
help
|
|
|
|
Enables support for the ASM9260 timer.
|
2015-02-23 11:54:16 -07:00
|
|
|
|
2012-10-18 06:01:25 -06:00
|
|
|
config CLKSRC_NOMADIK_MTU
|
2015-11-01 13:11:28 -07:00
|
|
|
bool "Nomakdik clocksource driver" if COMPILE_TEST
|
|
|
|
depends on ARM
|
2012-10-18 06:01:25 -06:00
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
Support for Multi Timer Unit. MTU provides access
|
|
|
|
to multiple interrupt generating programmable
|
|
|
|
32-bit free running decrementing counters.
|
|
|
|
|
2011-05-27 02:30:12 -06:00
|
|
|
config CLKSRC_DBX500_PRCMU
|
2015-11-01 13:16:01 -07:00
|
|
|
bool "Clocksource PRCMU Timer" if COMPILE_TEST
|
2016-01-25 15:24:19 -07:00
|
|
|
depends on HAS_IOMEM
|
2011-05-27 02:30:12 -06:00
|
|
|
help
|
|
|
|
Use the always on PRCMU Timer as clocksource
|
|
|
|
|
2016-06-02 12:06:54 -06:00
|
|
|
config CLPS711X_TIMER
|
|
|
|
bool "Cirrus logic timer driver" if COMPILE_TEST
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
Enables support for the Cirrus Logic PS711 timer.
|
|
|
|
|
2016-06-03 05:11:39 -06:00
|
|
|
config ATLAS7_TIMER
|
|
|
|
bool "Atlas7 timer driver" if COMPILE_TEST
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
Enables support for the Atlas7 timer.
|
|
|
|
|
2016-06-03 05:36:18 -06:00
|
|
|
config MXS_TIMER
|
|
|
|
bool "Mxs timer driver" if COMPILE_TEST
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
select STMP_DEVICE
|
|
|
|
help
|
|
|
|
Enables support for the Mxs timer.
|
|
|
|
|
2016-06-03 06:28:38 -06:00
|
|
|
config PRIMA2_TIMER
|
|
|
|
bool "Prima2 timer driver" if COMPILE_TEST
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
Enables support for the Prima2 timer.
|
|
|
|
|
2016-06-03 06:31:16 -06:00
|
|
|
config U300_TIMER
|
|
|
|
bool "U300 timer driver" if COMPILE_TEST
|
|
|
|
depends on ARM
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
Enables support for the U300 timer.
|
|
|
|
|
2016-06-03 07:03:21 -06:00
|
|
|
config NSPIRE_TIMER
|
|
|
|
bool "NSpire timer driver" if COMPILE_TEST
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
Enables support for the Nspire timer.
|
|
|
|
|
2016-06-03 07:05:05 -06:00
|
|
|
config KEYSTONE_TIMER
|
|
|
|
bool "Keystone timer driver" if COMPILE_TEST
|
|
|
|
depends on ARM || ARM64
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
Enables support for the Keystone timer.
|
|
|
|
|
2016-06-03 07:11:21 -06:00
|
|
|
config INTEGRATOR_AP_TIMER
|
|
|
|
bool "Integrator-ap timer driver" if COMPILE_TEST
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
Enables support for the Integrator-ap timer.
|
|
|
|
|
2013-10-03 13:56:29 -06:00
|
|
|
config CLKSRC_EFM32
|
|
|
|
bool "Clocksource for Energy Micro's EFM32 SoCs" if !ARCH_EFM32
|
|
|
|
depends on OF && ARM && (ARCH_EFM32 || COMPILE_TEST)
|
2013-11-19 19:15:11 -07:00
|
|
|
select CLKSRC_MMIO
|
2013-10-03 13:56:29 -06:00
|
|
|
default ARCH_EFM32
|
|
|
|
help
|
|
|
|
Support to use the timers of EFM32 SoCs as clock source and clock
|
|
|
|
event device.
|
|
|
|
|
2015-05-11 16:00:48 -06:00
|
|
|
config CLKSRC_LPC32XX
|
2015-10-31 14:44:52 -06:00
|
|
|
bool "Clocksource for LPC32XX" if COMPILE_TEST
|
clocksource: Improve GENERIC_CLOCKEVENTS dependency
We regularly run into build errors when a clocksource driver selects
CONFIG_TIMER_OF while CONFIG_GENERIC_CLOCKEVENTS is disabled:
In file included from drivers/clocksource/timer-of.c:25:0:
drivers/clocksource/timer-of.h:35:28: error: field 'clkevt' has incomplete type
At the moment, three drivers can show this behavior: ARMV7M_SYSTICK,
CLKSRC_ST_LPC and CLKSRC_NPS. We could add further dependencies as we did
many times, but I have looked a little bit more at what architectures
are left that don't use GENERIC_CLOCKEVENTS, and this shows that there
is a better solution.
On arch/frv and arch/ia64, we never select CONFIG_GENERIC_CLOCKEVENTS
and we also don't use ARCH_USES_GETTIMEOFFSET, which would
block the clocksource Kconfig menu. On m68k, some platforms use
CONFIG_GENERIC_CLOCKEVENTS, some use ARCH_USES_GETTIMEOFFSET, and some
use neither of them. The good news is that there is no configuration that
does not set CONFIG_GENERIC_CLOCKEVENTS but that wants to enable any of
the Kconfig symbols in the menu, so we can simply replace the dependency
with the stricter one. While in theory one could have a clocksource
driver without the clockevent infrastructure, this seems unlikely
to be relevant in the future any more.
We can probably drop some of the other dependencies as well now,
e.g. there should generally be no reason to depend on CONFIG_ARM
unless the driver uses architecture specific assembly.
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
2017-09-05 09:04:56 -06:00
|
|
|
depends on HAS_IOMEM
|
2016-02-09 18:54:27 -07:00
|
|
|
depends on ARM
|
2015-05-11 16:00:48 -06:00
|
|
|
select CLKSRC_MMIO
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2015-10-31 14:44:52 -06:00
|
|
|
help
|
|
|
|
Support for the LPC32XX clocksource.
|
2015-05-11 16:00:48 -06:00
|
|
|
|
2015-08-07 09:39:31 -06:00
|
|
|
config CLKSRC_PISTACHIO
|
2015-10-30 10:28:13 -06:00
|
|
|
bool "Clocksource for Pistachio SoC" if COMPILE_TEST
|
clocksource: Improve GENERIC_CLOCKEVENTS dependency
We regularly run into build errors when a clocksource driver selects
CONFIG_TIMER_OF while CONFIG_GENERIC_CLOCKEVENTS is disabled:
In file included from drivers/clocksource/timer-of.c:25:0:
drivers/clocksource/timer-of.h:35:28: error: field 'clkevt' has incomplete type
At the moment, three drivers can show this behavior: ARMV7M_SYSTICK,
CLKSRC_ST_LPC and CLKSRC_NPS. We could add further dependencies as we did
many times, but I have looked a little bit more at what architectures
are left that don't use GENERIC_CLOCKEVENTS, and this shows that there
is a better solution.
On arch/frv and arch/ia64, we never select CONFIG_GENERIC_CLOCKEVENTS
and we also don't use ARCH_USES_GETTIMEOFFSET, which would
block the clocksource Kconfig menu. On m68k, some platforms use
CONFIG_GENERIC_CLOCKEVENTS, some use ARCH_USES_GETTIMEOFFSET, and some
use neither of them. The good news is that there is no configuration that
does not set CONFIG_GENERIC_CLOCKEVENTS but that wants to enable any of
the Kconfig symbols in the menu, so we can simply replace the dependency
with the stricter one. While in theory one could have a clocksource
driver without the clockevent infrastructure, this seems unlikely
to be relevant in the future any more.
We can probably drop some of the other dependencies as well now,
e.g. there should generally be no reason to depend on CONFIG_ARM
unless the driver uses architecture specific assembly.
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
2017-09-05 09:04:56 -06:00
|
|
|
depends on HAS_IOMEM
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2015-10-30 10:28:13 -06:00
|
|
|
help
|
|
|
|
Enables the clocksource for the Pistachio SoC.
|
2015-08-07 09:39:31 -06:00
|
|
|
|
2015-09-29 12:55:33 -06:00
|
|
|
config CLKSRC_TI_32K
|
|
|
|
bool "Texas Instruments 32.768 Hz Clocksource" if COMPILE_TEST
|
2015-10-16 15:10:05 -06:00
|
|
|
depends on GENERIC_SCHED_CLOCK
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF if OF
|
2015-09-29 12:55:33 -06:00
|
|
|
help
|
|
|
|
This option enables support for Texas Instruments 32.768 Hz clocksource
|
|
|
|
available on many OMAP-like platforms.
|
|
|
|
|
2015-10-17 13:37:30 -06:00
|
|
|
config CLKSRC_NPS
|
|
|
|
bool "NPS400 clocksource driver" if COMPILE_TEST
|
|
|
|
depends on !PHYS_ADDR_T_64BIT
|
|
|
|
select CLKSRC_MMIO
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF if OF
|
2015-10-17 13:37:30 -06:00
|
|
|
help
|
|
|
|
NPS400 clocksource support.
|
|
|
|
Got 64 bit counter with update rate up to 1000MHz.
|
|
|
|
This counter is accessed via couple of 32 bit memory mapped registers.
|
|
|
|
|
2015-05-22 15:03:33 -06:00
|
|
|
config CLKSRC_STM32
|
2015-06-20 17:02:32 -06:00
|
|
|
bool "Clocksource for STM32 SoCs" if !ARCH_STM32
|
|
|
|
depends on OF && ARM && (ARCH_STM32 || COMPILE_TEST)
|
2015-05-22 15:03:33 -06:00
|
|
|
select CLKSRC_MMIO
|
2018-01-08 06:28:51 -07:00
|
|
|
select TIMER_OF
|
2015-05-22 15:03:33 -06:00
|
|
|
|
2016-04-25 02:45:44 -06:00
|
|
|
config CLKSRC_MPS2
|
|
|
|
bool "Clocksource for MPS2 SoCs" if COMPILE_TEST
|
|
|
|
depends on GENERIC_SCHED_CLOCK
|
|
|
|
select CLKSRC_MMIO
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2016-04-25 02:45:44 -06:00
|
|
|
|
2016-10-31 14:46:38 -06:00
|
|
|
config ARC_TIMERS
|
|
|
|
bool "Support for 32-bit TIMERn counters in ARC Cores" if COMPILE_TEST
|
2018-11-19 04:29:17 -07:00
|
|
|
depends on GENERIC_SCHED_CLOCK
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2016-10-31 14:46:38 -06:00
|
|
|
help
|
|
|
|
These are legacy 32-bit TIMER0 and TIMER1 counters found on all ARC cores
|
|
|
|
(ARC700 as well as ARC HS38).
|
|
|
|
TIMER0 serves as clockevent while TIMER1 provides clocksource
|
|
|
|
|
|
|
|
config ARC_TIMERS_64BIT
|
|
|
|
bool "Support for 64-bit counters in ARC HS38 cores" if COMPILE_TEST
|
|
|
|
depends on ARC_TIMERS
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2016-10-31 14:46:38 -06:00
|
|
|
help
|
|
|
|
This enables 2 different 64-bit timers: RTC (for UP) and GFRC (for SMP)
|
|
|
|
RTC is implemented inside the core, while GFRC sits outside the core in
|
|
|
|
ARConnect IP block. Driver automatically picks one of them for clocksource
|
|
|
|
as appropriate.
|
|
|
|
|
2012-11-12 07:33:44 -07:00
|
|
|
config ARM_ARCH_TIMER
|
|
|
|
bool
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF if OF
|
2017-05-26 11:40:24 -06:00
|
|
|
select TIMER_ACPI if ACPI
|
2012-10-09 03:54:39 -06:00
|
|
|
|
2013-08-23 08:32:29 -06:00
|
|
|
config ARM_ARCH_TIMER_EVTSTREAM
|
2016-06-27 10:30:13 -06:00
|
|
|
bool "Enable ARM architected timer event stream generation by default"
|
2013-08-23 08:32:29 -06:00
|
|
|
default y if ARM_ARCH_TIMER
|
2013-11-20 13:02:03 -07:00
|
|
|
depends on ARM_ARCH_TIMER
|
2013-08-23 08:32:29 -06:00
|
|
|
help
|
2016-06-27 10:30:13 -06:00
|
|
|
This option enables support by default for event stream generation
|
|
|
|
based on the ARM architected timer. It is used for waking up CPUs
|
|
|
|
executing the wfe instruction at a frequency represented as a
|
|
|
|
power-of-2 divisor of the clock rate. The behaviour can also be
|
|
|
|
overridden on the command line using the
|
|
|
|
clocksource.arm_arch_timer.evtstream parameter.
|
2013-08-23 08:32:29 -06:00
|
|
|
The main use of the event stream is wfe-based timeouts of userspace
|
|
|
|
locking implementations. It might also be useful for imposing timeout
|
|
|
|
on wfe to safeguard against any programming errors in case an expected
|
|
|
|
event is not generated.
|
|
|
|
This must be disabled for hardware validation purposes to detect any
|
|
|
|
hardware anomalies of missing events.
|
|
|
|
|
2017-02-06 09:47:41 -07:00
|
|
|
config ARM_ARCH_TIMER_OOL_WORKAROUND
|
|
|
|
bool
|
|
|
|
|
2016-09-22 02:35:17 -06:00
|
|
|
config FSL_ERRATUM_A008585
|
|
|
|
bool "Workaround for Freescale/NXP Erratum A-008585"
|
|
|
|
default y
|
|
|
|
depends on ARM_ARCH_TIMER && ARM64
|
2017-02-06 09:47:41 -07:00
|
|
|
select ARM_ARCH_TIMER_OOL_WORKAROUND
|
2016-09-22 02:35:17 -06:00
|
|
|
help
|
|
|
|
This option enables a workaround for Freescale/NXP Erratum
|
|
|
|
A-008585 ("ARM generic timer may contain an erroneous
|
|
|
|
value"). The workaround will only be active if the
|
|
|
|
fsl,erratum-a008585 property is found in the timer node.
|
|
|
|
|
2017-02-06 09:47:42 -07:00
|
|
|
config HISILICON_ERRATUM_161010101
|
|
|
|
bool "Workaround for Hisilicon Erratum 161010101"
|
|
|
|
default y
|
|
|
|
select ARM_ARCH_TIMER_OOL_WORKAROUND
|
|
|
|
depends on ARM_ARCH_TIMER && ARM64
|
|
|
|
help
|
|
|
|
This option enables a workaround for Hisilicon Erratum
|
|
|
|
161010101. The workaround will be active if the hisilicon,erratum-161010101
|
|
|
|
property is found in the timer node.
|
|
|
|
|
2017-01-27 05:52:31 -07:00
|
|
|
config ARM64_ERRATUM_858921
|
|
|
|
bool "Workaround for Cortex-A73 erratum 858921"
|
|
|
|
default y
|
|
|
|
select ARM_ARCH_TIMER_OOL_WORKAROUND
|
|
|
|
depends on ARM_ARCH_TIMER && ARM64
|
|
|
|
help
|
|
|
|
This option enables a workaround applicable to Cortex-A73
|
|
|
|
(all versions), whose counter may return incorrect values.
|
|
|
|
The workaround will be dynamically enabled when an affected
|
|
|
|
core is detected.
|
|
|
|
|
clocksource/drivers/arch_timer: Workaround for Allwinner A64 timer instability
The Allwinner A64 SoC is known[1] to have an unstable architectural
timer, which manifests itself most obviously in the time jumping forward
a multiple of 95 years[2][3]. This coincides with 2^56 cycles at a
timer frequency of 24 MHz, implying that the time went slightly backward
(and this was interpreted by the kernel as it jumping forward and
wrapping around past the epoch).
Investigation revealed instability in the low bits of CNTVCT at the
point a high bit rolls over. This leads to power-of-two cycle forward
and backward jumps. (Testing shows that forward jumps are about twice as
likely as backward jumps.) Since the counter value returns to normal
after an indeterminate read, each "jump" really consists of both a
forward and backward jump from the software perspective.
Unless the kernel is trapping CNTVCT reads, a userspace program is able
to read the register in a loop faster than it changes. A test program
running on all 4 CPU cores that reported jumps larger than 100 ms was
run for 13.6 hours and reported the following:
Count | Event
-------+---------------------------
9940 | jumped backward 699ms
268 | jumped backward 1398ms
1 | jumped backward 2097ms
16020 | jumped forward 175ms
6443 | jumped forward 699ms
2976 | jumped forward 1398ms
9 | jumped forward 356516ms
9 | jumped forward 357215ms
4 | jumped forward 714430ms
1 | jumped forward 3578440ms
This works out to a jump larger than 100 ms about every 5.5 seconds on
each CPU core.
The largest jump (almost an hour!) was the following sequence of reads:
0x0000007fffffffff → 0x00000093feffffff → 0x0000008000000000
Note that the middle bits don't necessarily all read as all zeroes or
all ones during the anomalous behavior; however the low 10 bits checked
by the function in this patch have never been observed with any other
value.
Also note that smaller jumps are much more common, with backward jumps
of 2048 (2^11) cycles observed over 400 times per second on each core.
(Of course, this is partially explained by lower bits rolling over more
frequently.) Any one of these could have caused the 95 year time skip.
Similar anomalies were observed while reading CNTPCT (after patching the
kernel to allow reads from userspace). However, the CNTPCT jumps are
much less frequent, and only small jumps were observed. The same program
as before (except now reading CNTPCT) observed after 72 hours:
Count | Event
-------+---------------------------
17 | jumped backward 699ms
52 | jumped forward 175ms
2831 | jumped forward 699ms
5 | jumped forward 1398ms
Further investigation showed that the instability in CNTPCT/CNTVCT also
affected the respective timer's TVAL register. The following values were
observed immediately after writing CNVT_TVAL to 0x10000000:
CNTVCT | CNTV_TVAL | CNTV_CVAL | CNTV_TVAL Error
--------------------+------------+--------------------+-----------------
0x000000d4a2d8bfff | 0x10003fff | 0x000000d4b2d8bfff | +0x00004000
0x000000d4a2d94000 | 0x0fffffff | 0x000000d4b2d97fff | -0x00004000
0x000000d4a2d97fff | 0x10003fff | 0x000000d4b2d97fff | +0x00004000
0x000000d4a2d9c000 | 0x0fffffff | 0x000000d4b2d9ffff | -0x00004000
The pattern of errors in CNTV_TVAL seemed to depend on exactly which
value was written to it. For example, after writing 0x10101010:
CNTVCT | CNTV_TVAL | CNTV_CVAL | CNTV_TVAL Error
--------------------+------------+--------------------+-----------------
0x000001ac3effffff | 0x1110100f | 0x000001ac4f10100f | +0x1000000
0x000001ac40000000 | 0x1010100f | 0x000001ac5110100f | -0x1000000
0x000001ac58ffffff | 0x1110100f | 0x000001ac6910100f | +0x1000000
0x000001ac66000000 | 0x1010100f | 0x000001ac7710100f | -0x1000000
0x000001ac6affffff | 0x1110100f | 0x000001ac7b10100f | +0x1000000
0x000001ac6e000000 | 0x1010100f | 0x000001ac7f10100f | -0x1000000
I was also twice able to reproduce the issue covered by Allwinner's
workaround[4], that writing to TVAL sometimes fails, and both CVAL and
TVAL are left with entirely bogus values. One was the following values:
CNTVCT | CNTV_TVAL | CNTV_CVAL
--------------------+------------+--------------------------------------
0x000000d4a2d6014c | 0x8fbd5721 | 0x000000d132935fff (615s in the past)
Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
========================================================================
Because the CPU can read the CNTPCT/CNTVCT registers faster than they
change, performing two reads of the register and comparing the high bits
(like other workarounds) is not a workable solution. And because the
timer can jump both forward and backward, no pair of reads can
distinguish a good value from a bad one. The only way to guarantee a
good value from consecutive reads would be to read _three_ times, and
take the middle value only if the three values are 1) each unique and
2) increasing. This takes at minimum 3 counter cycles (125 ns), or more
if an anomaly is detected.
However, since there is a distinct pattern to the bad values, we can
optimize the common case (1022/1024 of the time) to a single read by
simply ignoring values that match the error pattern. This still takes no
more than 3 cycles in the worst case, and requires much less code. As an
additional safety check, we still limit the loop iteration to the number
of max-frequency (1.2 GHz) CPU cycles in three 24 MHz counter periods.
For the TVAL registers, the simple solution is to not use them. Instead,
read or write the CVAL and calculate the TVAL value in software.
Although the manufacturer is aware of at least part of the erratum[4],
there is no official name for it. For now, use the kernel-internal name
"UNKNOWN1".
[1]: https://github.com/armbian/build/commit/a08cd6fe7ae9
[2]: https://forum.armbian.com/topic/3458-a64-datetime-clock-issue/
[3]: https://irclog.whitequark.org/linux-sunxi/2018-01-26
[4]: https://github.com/Allwinner-Homlet/H6-BSP4.9-linux/blob/master/drivers/clocksource/arm_arch_timer.c#L272
Acked-by: Maxime Ripard <maxime.ripard@bootlin.com>
Tested-by: Andre Przywara <andre.przywara@arm.com>
Signed-off-by: Samuel Holland <samuel@sholland.org>
Cc: stable@vger.kernel.org
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
2019-01-12 19:17:18 -07:00
|
|
|
config SUN50I_ERRATUM_UNKNOWN1
|
|
|
|
bool "Workaround for Allwinner A64 erratum UNKNOWN1"
|
|
|
|
default y
|
|
|
|
depends on ARM_ARCH_TIMER && ARM64 && ARCH_SUNXI
|
|
|
|
select ARM_ARCH_TIMER_OOL_WORKAROUND
|
|
|
|
help
|
|
|
|
This option enables a workaround for instability in the timer on
|
|
|
|
the Allwinner A64 SoC. The workaround will only be active if the
|
|
|
|
allwinner,erratum-unknown1 property is found in the timer node.
|
|
|
|
|
2013-06-26 05:48:38 -06:00
|
|
|
config ARM_GLOBAL_TIMER
|
2016-06-06 06:34:28 -06:00
|
|
|
bool "Support for the ARM global timer" if COMPILE_TEST
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF if OF
|
2016-06-06 06:34:28 -06:00
|
|
|
depends on ARM
|
2013-06-26 05:48:38 -06:00
|
|
|
help
|
|
|
|
This options enables support for the ARM global timer unit
|
|
|
|
|
2015-05-18 09:29:40 -06:00
|
|
|
config ARM_TIMER_SP804
|
2019-04-08 02:07:45 -06:00
|
|
|
bool "Support for Dual Timer SP804 module" if COMPILE_TEST
|
2015-06-23 21:49:05 -06:00
|
|
|
depends on GENERIC_SCHED_CLOCK && CLKDEV_LOOKUP
|
2015-05-18 09:29:40 -06:00
|
|
|
select CLKSRC_MMIO
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF if OF
|
2015-05-18 09:29:40 -06:00
|
|
|
|
2013-06-26 05:48:38 -06:00
|
|
|
config CLKSRC_ARM_GLOBAL_TIMER_SCHED_CLOCK
|
|
|
|
bool
|
|
|
|
depends on ARM_GLOBAL_TIMER
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
Use ARM global timer clock source as sched_clock
|
|
|
|
|
2015-05-09 01:53:46 -06:00
|
|
|
config ARMV7M_SYSTICK
|
2016-06-02 10:41:52 -06:00
|
|
|
bool "Support for the ARMv7M system time" if COMPILE_TEST
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF if OF
|
2015-05-09 01:53:46 -06:00
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
This options enables support for the ARMv7M system timer unit
|
|
|
|
|
2014-09-02 10:12:35 -06:00
|
|
|
config ATMEL_PIT
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF if OF
|
2014-09-02 10:12:35 -06:00
|
|
|
def_bool SOC_AT91SAM9 || SOC_SAMA5
|
|
|
|
|
2015-03-12 06:07:31 -06:00
|
|
|
config ATMEL_ST
|
2016-06-06 11:08:39 -06:00
|
|
|
bool "Atmel ST timer support" if COMPILE_TEST
|
2018-03-06 04:20:33 -07:00
|
|
|
depends on HAS_IOMEM
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2015-03-19 07:17:48 -06:00
|
|
|
select MFD_SYSCON
|
2016-06-06 11:08:39 -06:00
|
|
|
help
|
|
|
|
Support for the Atmel ST timer.
|
2015-03-12 06:07:31 -06:00
|
|
|
|
2019-04-26 15:47:14 -06:00
|
|
|
config ATMEL_TCB_CLKSRC
|
|
|
|
bool "Atmel TC Block timer driver" if COMPILE_TEST
|
|
|
|
depends on HAS_IOMEM
|
|
|
|
select TIMER_OF if OF
|
|
|
|
help
|
|
|
|
Support for Timer Counter Blocks on Atmel SoCs.
|
|
|
|
|
2013-03-09 00:16:13 -07:00
|
|
|
config CLKSRC_EXYNOS_MCT
|
2015-11-01 13:51:30 -07:00
|
|
|
bool "Exynos multi core timer driver" if COMPILE_TEST
|
2016-08-24 07:49:05 -06:00
|
|
|
depends on ARM || ARM64
|
2013-03-09 00:16:13 -07:00
|
|
|
help
|
|
|
|
Support for Multi Core Timer controller on Exynos SoCs.
|
2013-05-06 15:49:09 -06:00
|
|
|
|
2013-04-20 15:22:13 -06:00
|
|
|
config CLKSRC_SAMSUNG_PWM
|
2016-06-16 07:53:18 -06:00
|
|
|
bool "PWM timer driver for Samsung S3C, S5P" if COMPILE_TEST
|
2016-01-25 15:24:19 -07:00
|
|
|
depends on HAS_IOMEM
|
2013-04-20 15:22:13 -06:00
|
|
|
help
|
|
|
|
This is a new clocksource driver for the PWM timer found in
|
|
|
|
Samsung S3C, S5P and Exynos SoCs, replacing an earlier driver
|
|
|
|
for all devicetree enabled platforms. This driver will be
|
|
|
|
needed only on systems that do not have the Exynos MCT available.
|
2013-05-29 02:12:17 -06:00
|
|
|
|
2014-05-23 02:12:04 -06:00
|
|
|
config FSL_FTM_TIMER
|
2015-11-02 01:51:02 -07:00
|
|
|
bool "Freescale FlexTimer Module driver" if COMPILE_TEST
|
2016-01-25 15:24:19 -07:00
|
|
|
depends on HAS_IOMEM
|
2016-01-08 06:21:31 -07:00
|
|
|
select CLKSRC_MMIO
|
2014-05-23 02:12:04 -06:00
|
|
|
help
|
|
|
|
Support for Freescale FlexTimer Module (FTM) timer.
|
|
|
|
|
2013-05-29 02:12:17 -06:00
|
|
|
config VF_PIT_TIMER
|
|
|
|
bool
|
2016-01-25 09:02:49 -07:00
|
|
|
select CLKSRC_MMIO
|
2013-05-29 02:12:17 -06:00
|
|
|
help
|
|
|
|
Support for Period Interrupt Timer on Freescale Vybrid Family SoCs.
|
2014-02-20 04:54:45 -07:00
|
|
|
|
2016-06-15 04:13:26 -06:00
|
|
|
config OXNAS_RPS_TIMER
|
|
|
|
bool "Oxford Semiconductor OXNAS RPS Timers driver" if COMPILE_TEST
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2016-06-15 04:13:26 -06:00
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
This enables support for the Oxford Semiconductor OXNAS RPS timers.
|
|
|
|
|
2014-02-20 04:54:45 -07:00
|
|
|
config SYS_SUPPORTS_SH_CMT
|
|
|
|
bool
|
|
|
|
|
2014-07-18 03:36:43 -06:00
|
|
|
config MTK_TIMER
|
2015-10-30 10:53:27 -06:00
|
|
|
bool "Mediatek timer driver" if COMPILE_TEST
|
clocksource: Improve GENERIC_CLOCKEVENTS dependency
We regularly run into build errors when a clocksource driver selects
CONFIG_TIMER_OF while CONFIG_GENERIC_CLOCKEVENTS is disabled:
In file included from drivers/clocksource/timer-of.c:25:0:
drivers/clocksource/timer-of.h:35:28: error: field 'clkevt' has incomplete type
At the moment, three drivers can show this behavior: ARMV7M_SYSTICK,
CLKSRC_ST_LPC and CLKSRC_NPS. We could add further dependencies as we did
many times, but I have looked a little bit more at what architectures
are left that don't use GENERIC_CLOCKEVENTS, and this shows that there
is a better solution.
On arch/frv and arch/ia64, we never select CONFIG_GENERIC_CLOCKEVENTS
and we also don't use ARCH_USES_GETTIMEOFFSET, which would
block the clocksource Kconfig menu. On m68k, some platforms use
CONFIG_GENERIC_CLOCKEVENTS, some use ARCH_USES_GETTIMEOFFSET, and some
use neither of them. The good news is that there is no configuration that
does not set CONFIG_GENERIC_CLOCKEVENTS but that wants to enable any of
the Kconfig symbols in the menu, so we can simply replace the dependency
with the stricter one. While in theory one could have a clocksource
driver without the clockevent infrastructure, this seems unlikely
to be relevant in the future any more.
We can probably drop some of the other dependencies as well now,
e.g. there should generally be no reason to depend on CONFIG_ARM
unless the driver uses architecture specific assembly.
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
2017-09-05 09:04:56 -06:00
|
|
|
depends on HAS_IOMEM
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2014-07-18 03:36:43 -06:00
|
|
|
select CLKSRC_MMIO
|
2015-10-30 10:53:27 -06:00
|
|
|
help
|
|
|
|
Support for Mediatek timer driver.
|
2014-07-18 03:36:43 -06:00
|
|
|
|
2018-01-08 06:28:47 -07:00
|
|
|
config SPRD_TIMER
|
2018-05-07 03:04:47 -06:00
|
|
|
bool "Spreadtrum timer driver" if EXPERT
|
2018-01-08 06:28:47 -07:00
|
|
|
depends on HAS_IOMEM
|
2018-05-07 03:04:47 -06:00
|
|
|
depends on (ARCH_SPRD || COMPILE_TEST)
|
|
|
|
default ARCH_SPRD
|
2018-01-08 06:28:47 -07:00
|
|
|
select TIMER_OF
|
|
|
|
help
|
|
|
|
Enables support for the Spreadtrum timer driver.
|
|
|
|
|
2014-02-20 04:54:45 -07:00
|
|
|
config SYS_SUPPORTS_SH_MTU2
|
|
|
|
bool
|
|
|
|
|
|
|
|
config SYS_SUPPORTS_SH_TMU
|
|
|
|
bool
|
|
|
|
|
|
|
|
config SYS_SUPPORTS_EM_STI
|
|
|
|
bool
|
|
|
|
|
2016-10-13 15:51:06 -06:00
|
|
|
config CLKSRC_JCORE_PIT
|
|
|
|
bool "J-Core PIT timer driver" if COMPILE_TEST
|
|
|
|
depends on OF
|
|
|
|
depends on HAS_IOMEM
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
This enables build of clocksource and clockevent driver for
|
|
|
|
the integrated PIT in the J-Core synthesizable, open source SoC.
|
|
|
|
|
2014-02-20 04:54:45 -07:00
|
|
|
config SH_TIMER_CMT
|
|
|
|
bool "Renesas CMT timer driver" if COMPILE_TEST
|
2015-03-26 03:27:06 -06:00
|
|
|
depends on HAS_IOMEM
|
2014-02-20 04:54:45 -07:00
|
|
|
default SYS_SUPPORTS_SH_CMT
|
|
|
|
help
|
|
|
|
This enables build of a clocksource and clockevent driver for
|
|
|
|
the Compare Match Timer (CMT) hardware available in 16/32/48-bit
|
|
|
|
variants on a wide range of Mobile and Automotive SoCs from Renesas.
|
|
|
|
|
|
|
|
config SH_TIMER_MTU2
|
|
|
|
bool "Renesas MTU2 timer driver" if COMPILE_TEST
|
2015-03-26 03:27:06 -06:00
|
|
|
depends on HAS_IOMEM
|
2014-02-20 04:54:45 -07:00
|
|
|
default SYS_SUPPORTS_SH_MTU2
|
|
|
|
help
|
|
|
|
This enables build of a clockevent driver for the Multi-Function
|
2014-07-18 03:36:36 -06:00
|
|
|
Timer Pulse Unit 2 (MTU2) hardware available on SoCs from Renesas.
|
2014-02-20 04:54:45 -07:00
|
|
|
This hardware comes with 16 bit-timer registers.
|
|
|
|
|
2017-01-27 13:02:15 -07:00
|
|
|
config RENESAS_OSTM
|
|
|
|
bool "Renesas OSTM timer driver" if COMPILE_TEST
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
Enables the support for the Renesas OSTM.
|
|
|
|
|
2014-02-20 04:54:45 -07:00
|
|
|
config SH_TIMER_TMU
|
|
|
|
bool "Renesas TMU timer driver" if COMPILE_TEST
|
2015-03-26 03:27:06 -06:00
|
|
|
depends on HAS_IOMEM
|
2014-02-20 04:54:45 -07:00
|
|
|
default SYS_SUPPORTS_SH_TMU
|
|
|
|
help
|
|
|
|
This enables build of a clocksource and clockevent driver for
|
|
|
|
the 32-bit Timer Unit (TMU) hardware available on a wide range
|
|
|
|
SoCs from Renesas.
|
|
|
|
|
|
|
|
config EM_TIMER_STI
|
|
|
|
bool "Renesas STI timer driver" if COMPILE_TEST
|
clocksource: Improve GENERIC_CLOCKEVENTS dependency
We regularly run into build errors when a clocksource driver selects
CONFIG_TIMER_OF while CONFIG_GENERIC_CLOCKEVENTS is disabled:
In file included from drivers/clocksource/timer-of.c:25:0:
drivers/clocksource/timer-of.h:35:28: error: field 'clkevt' has incomplete type
At the moment, three drivers can show this behavior: ARMV7M_SYSTICK,
CLKSRC_ST_LPC and CLKSRC_NPS. We could add further dependencies as we did
many times, but I have looked a little bit more at what architectures
are left that don't use GENERIC_CLOCKEVENTS, and this shows that there
is a better solution.
On arch/frv and arch/ia64, we never select CONFIG_GENERIC_CLOCKEVENTS
and we also don't use ARCH_USES_GETTIMEOFFSET, which would
block the clocksource Kconfig menu. On m68k, some platforms use
CONFIG_GENERIC_CLOCKEVENTS, some use ARCH_USES_GETTIMEOFFSET, and some
use neither of them. The good news is that there is no configuration that
does not set CONFIG_GENERIC_CLOCKEVENTS but that wants to enable any of
the Kconfig symbols in the menu, so we can simply replace the dependency
with the stricter one. While in theory one could have a clocksource
driver without the clockevent infrastructure, this seems unlikely
to be relevant in the future any more.
We can probably drop some of the other dependencies as well now,
e.g. there should generally be no reason to depend on CONFIG_ARM
unless the driver uses architecture specific assembly.
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
2017-09-05 09:04:56 -06:00
|
|
|
depends on HAS_IOMEM
|
2014-02-20 04:54:45 -07:00
|
|
|
default SYS_SUPPORTS_EM_STI
|
|
|
|
help
|
|
|
|
This enables build of a clocksource and clockevent driver for
|
|
|
|
the 48-bit System Timer (STI) hardware available on a SoCs
|
|
|
|
such as EMEV2 from former NEC Electronics.
|
2014-04-05 14:51:19 -06:00
|
|
|
|
2014-01-29 15:17:30 -07:00
|
|
|
config CLKSRC_QCOM
|
2015-10-09 03:10:43 -06:00
|
|
|
bool "Qualcomm MSM timer" if COMPILE_TEST
|
|
|
|
depends on ARM
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2015-10-09 03:10:43 -06:00
|
|
|
help
|
|
|
|
This enables the clocksource and the per CPU clockevent driver for the
|
|
|
|
Qualcomm SoCs.
|
2014-04-16 11:22:59 -06:00
|
|
|
|
|
|
|
config CLKSRC_VERSATILE
|
2016-06-07 03:05:01 -06:00
|
|
|
bool "ARM Versatile (Express) reference platforms clock source" if COMPILE_TEST
|
|
|
|
depends on GENERIC_SCHED_CLOCK && !ARCH_USES_GETTIMEOFFSET
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2014-04-16 11:22:59 -06:00
|
|
|
default y if MFD_VEXPRESS_SYSREG
|
|
|
|
help
|
|
|
|
This option enables clock source based on free running
|
|
|
|
counter available in the "System Registers" block of
|
|
|
|
ARM Versatile, RealView and Versatile Express reference
|
|
|
|
platforms.
|
2014-06-16 03:48:45 -06:00
|
|
|
|
2014-10-20 13:03:58 -06:00
|
|
|
config CLKSRC_MIPS_GIC
|
|
|
|
bool
|
|
|
|
depends on MIPS_GIC
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2014-10-20 13:03:58 -06:00
|
|
|
|
2015-10-09 08:59:18 -06:00
|
|
|
config CLKSRC_TANGO_XTAL
|
2015-10-29 13:54:19 -06:00
|
|
|
bool "Clocksource for Tango SoC" if COMPILE_TEST
|
|
|
|
depends on ARM
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF
|
2015-11-13 02:44:38 -07:00
|
|
|
select CLKSRC_MMIO
|
2015-10-29 13:54:19 -06:00
|
|
|
help
|
|
|
|
This enables the clocksource for Tango SoC
|
2015-10-09 08:59:18 -06:00
|
|
|
|
2014-12-21 08:07:09 -07:00
|
|
|
config CLKSRC_PXA
|
2015-10-09 09:47:32 -06:00
|
|
|
bool "Clocksource for PXA or SA-11x0 platform" if COMPILE_TEST
|
2016-01-25 15:24:19 -07:00
|
|
|
depends on HAS_IOMEM
|
2015-10-09 09:47:32 -06:00
|
|
|
select CLKSRC_MMIO
|
2014-12-21 08:07:09 -07:00
|
|
|
help
|
|
|
|
This enables OST0 support available on PXA and SA-11x0
|
|
|
|
platforms.
|
2015-01-27 10:52:42 -07:00
|
|
|
|
2015-11-09 06:43:52 -07:00
|
|
|
config H8300_TMR8
|
2015-11-09 07:18:08 -07:00
|
|
|
bool "Clockevent timer for the H8300 platform" if COMPILE_TEST
|
clocksource: Improve GENERIC_CLOCKEVENTS dependency
We regularly run into build errors when a clocksource driver selects
CONFIG_TIMER_OF while CONFIG_GENERIC_CLOCKEVENTS is disabled:
In file included from drivers/clocksource/timer-of.c:25:0:
drivers/clocksource/timer-of.h:35:28: error: field 'clkevt' has incomplete type
At the moment, three drivers can show this behavior: ARMV7M_SYSTICK,
CLKSRC_ST_LPC and CLKSRC_NPS. We could add further dependencies as we did
many times, but I have looked a little bit more at what architectures
are left that don't use GENERIC_CLOCKEVENTS, and this shows that there
is a better solution.
On arch/frv and arch/ia64, we never select CONFIG_GENERIC_CLOCKEVENTS
and we also don't use ARCH_USES_GETTIMEOFFSET, which would
block the clocksource Kconfig menu. On m68k, some platforms use
CONFIG_GENERIC_CLOCKEVENTS, some use ARCH_USES_GETTIMEOFFSET, and some
use neither of them. The good news is that there is no configuration that
does not set CONFIG_GENERIC_CLOCKEVENTS but that wants to enable any of
the Kconfig symbols in the menu, so we can simply replace the dependency
with the stricter one. While in theory one could have a clocksource
driver without the clockevent infrastructure, this seems unlikely
to be relevant in the future any more.
We can probably drop some of the other dependencies as well now,
e.g. there should generally be no reason to depend on CONFIG_ARM
unless the driver uses architecture specific assembly.
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
2017-09-05 09:04:56 -06:00
|
|
|
depends on HAS_IOMEM
|
2015-11-09 07:18:08 -07:00
|
|
|
help
|
|
|
|
This enables the 8 bits timer for the H8300 platform.
|
2015-11-09 06:43:52 -07:00
|
|
|
|
2015-01-27 10:52:42 -07:00
|
|
|
config H8300_TMR16
|
2015-11-09 07:18:08 -07:00
|
|
|
bool "Clockevent timer for the H83069 platform" if COMPILE_TEST
|
clocksource: Improve GENERIC_CLOCKEVENTS dependency
We regularly run into build errors when a clocksource driver selects
CONFIG_TIMER_OF while CONFIG_GENERIC_CLOCKEVENTS is disabled:
In file included from drivers/clocksource/timer-of.c:25:0:
drivers/clocksource/timer-of.h:35:28: error: field 'clkevt' has incomplete type
At the moment, three drivers can show this behavior: ARMV7M_SYSTICK,
CLKSRC_ST_LPC and CLKSRC_NPS. We could add further dependencies as we did
many times, but I have looked a little bit more at what architectures
are left that don't use GENERIC_CLOCKEVENTS, and this shows that there
is a better solution.
On arch/frv and arch/ia64, we never select CONFIG_GENERIC_CLOCKEVENTS
and we also don't use ARCH_USES_GETTIMEOFFSET, which would
block the clocksource Kconfig menu. On m68k, some platforms use
CONFIG_GENERIC_CLOCKEVENTS, some use ARCH_USES_GETTIMEOFFSET, and some
use neither of them. The good news is that there is no configuration that
does not set CONFIG_GENERIC_CLOCKEVENTS but that wants to enable any of
the Kconfig symbols in the menu, so we can simply replace the dependency
with the stricter one. While in theory one could have a clocksource
driver without the clockevent infrastructure, this seems unlikely
to be relevant in the future any more.
We can probably drop some of the other dependencies as well now,
e.g. there should generally be no reason to depend on CONFIG_ARM
unless the driver uses architecture specific assembly.
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
2017-09-05 09:04:56 -06:00
|
|
|
depends on HAS_IOMEM
|
2015-11-09 07:18:08 -07:00
|
|
|
help
|
|
|
|
This enables the 16 bits timer for the H8300 platform with the
|
|
|
|
H83069 cpu.
|
2015-01-27 10:52:42 -07:00
|
|
|
|
|
|
|
config H8300_TPU
|
2015-11-09 07:18:08 -07:00
|
|
|
bool "Clocksource for the H8300 platform" if COMPILE_TEST
|
clocksource: Improve GENERIC_CLOCKEVENTS dependency
We regularly run into build errors when a clocksource driver selects
CONFIG_TIMER_OF while CONFIG_GENERIC_CLOCKEVENTS is disabled:
In file included from drivers/clocksource/timer-of.c:25:0:
drivers/clocksource/timer-of.h:35:28: error: field 'clkevt' has incomplete type
At the moment, three drivers can show this behavior: ARMV7M_SYSTICK,
CLKSRC_ST_LPC and CLKSRC_NPS. We could add further dependencies as we did
many times, but I have looked a little bit more at what architectures
are left that don't use GENERIC_CLOCKEVENTS, and this shows that there
is a better solution.
On arch/frv and arch/ia64, we never select CONFIG_GENERIC_CLOCKEVENTS
and we also don't use ARCH_USES_GETTIMEOFFSET, which would
block the clocksource Kconfig menu. On m68k, some platforms use
CONFIG_GENERIC_CLOCKEVENTS, some use ARCH_USES_GETTIMEOFFSET, and some
use neither of them. The good news is that there is no configuration that
does not set CONFIG_GENERIC_CLOCKEVENTS but that wants to enable any of
the Kconfig symbols in the menu, so we can simply replace the dependency
with the stricter one. While in theory one could have a clocksource
driver without the clockevent infrastructure, this seems unlikely
to be relevant in the future any more.
We can probably drop some of the other dependencies as well now,
e.g. there should generally be no reason to depend on CONFIG_ARM
unless the driver uses architecture specific assembly.
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
2017-09-05 09:04:56 -06:00
|
|
|
depends on HAS_IOMEM
|
2015-11-09 07:18:08 -07:00
|
|
|
help
|
|
|
|
This enables the clocksource for the H8300 platform with the
|
|
|
|
H8S2678 cpu.
|
2015-01-27 10:52:42 -07:00
|
|
|
|
2015-05-15 01:41:00 -06:00
|
|
|
config CLKSRC_IMX_GPT
|
|
|
|
bool "Clocksource using i.MX GPT" if COMPILE_TEST
|
2018-11-04 18:10:27 -07:00
|
|
|
depends on (ARM || ARM64) && CLKDEV_LOOKUP
|
2015-05-15 01:41:00 -06:00
|
|
|
select CLKSRC_MMIO
|
|
|
|
|
2017-08-01 02:40:17 -06:00
|
|
|
config CLKSRC_IMX_TPM
|
|
|
|
bool "Clocksource using i.MX TPM" if COMPILE_TEST
|
clocksource: Improve GENERIC_CLOCKEVENTS dependency
We regularly run into build errors when a clocksource driver selects
CONFIG_TIMER_OF while CONFIG_GENERIC_CLOCKEVENTS is disabled:
In file included from drivers/clocksource/timer-of.c:25:0:
drivers/clocksource/timer-of.h:35:28: error: field 'clkevt' has incomplete type
At the moment, three drivers can show this behavior: ARMV7M_SYSTICK,
CLKSRC_ST_LPC and CLKSRC_NPS. We could add further dependencies as we did
many times, but I have looked a little bit more at what architectures
are left that don't use GENERIC_CLOCKEVENTS, and this shows that there
is a better solution.
On arch/frv and arch/ia64, we never select CONFIG_GENERIC_CLOCKEVENTS
and we also don't use ARCH_USES_GETTIMEOFFSET, which would
block the clocksource Kconfig menu. On m68k, some platforms use
CONFIG_GENERIC_CLOCKEVENTS, some use ARCH_USES_GETTIMEOFFSET, and some
use neither of them. The good news is that there is no configuration that
does not set CONFIG_GENERIC_CLOCKEVENTS but that wants to enable any of
the Kconfig symbols in the menu, so we can simply replace the dependency
with the stricter one. While in theory one could have a clocksource
driver without the clockevent infrastructure, this seems unlikely
to be relevant in the future any more.
We can probably drop some of the other dependencies as well now,
e.g. there should generally be no reason to depend on CONFIG_ARM
unless the driver uses architecture specific assembly.
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
2017-09-05 09:04:56 -06:00
|
|
|
depends on ARM && CLKDEV_LOOKUP
|
2017-08-01 02:40:17 -06:00
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
Enable this option to use IMX Timer/PWM Module (TPM) timer as
|
|
|
|
clocksource.
|
|
|
|
|
2015-05-26 06:39:43 -06:00
|
|
|
config CLKSRC_ST_LPC
|
2015-10-09 07:36:28 -06:00
|
|
|
bool "Low power clocksource found in the LPC" if COMPILE_TEST
|
2017-05-26 11:34:11 -06:00
|
|
|
select TIMER_OF if OF
|
2016-01-02 15:06:36 -07:00
|
|
|
depends on HAS_IOMEM
|
2016-01-25 09:02:49 -07:00
|
|
|
select CLKSRC_MMIO
|
2015-05-26 06:39:43 -06:00
|
|
|
help
|
|
|
|
Enable this option to use the Low Power controller timer
|
|
|
|
as clocksource.
|
|
|
|
|
2017-12-11 00:53:15 -07:00
|
|
|
config ATCPIT100_TIMER
|
|
|
|
bool "ATCPIT100 timer driver"
|
|
|
|
depends on NDS32 || COMPILE_TEST
|
|
|
|
depends on HAS_IOMEM
|
|
|
|
select TIMER_OF
|
|
|
|
default NDS32
|
|
|
|
help
|
|
|
|
This option enables support for the Andestech ATCPIT100 timers.
|
|
|
|
|
2018-08-04 02:23:19 -06:00
|
|
|
config RISCV_TIMER
|
|
|
|
bool "Timer for the RISC-V platform"
|
2018-12-04 03:29:52 -07:00
|
|
|
depends on GENERIC_SCHED_CLOCK && RISCV
|
2018-08-04 02:23:19 -06:00
|
|
|
default y
|
|
|
|
select TIMER_PROBE
|
|
|
|
select TIMER_OF
|
|
|
|
help
|
|
|
|
This enables the per-hart timer built into all RISC-V systems, which
|
|
|
|
is accessed via both the SBI and the rdcycle instruction. This is
|
|
|
|
required for all RISC-V systems.
|
|
|
|
|
2018-11-02 10:51:28 -06:00
|
|
|
config CSKY_MP_TIMER
|
|
|
|
bool "SMP Timer for the C-SKY platform" if COMPILE_TEST
|
|
|
|
depends on CSKY
|
|
|
|
select TIMER_OF
|
|
|
|
help
|
|
|
|
Say yes here to enable C-SKY SMP timer driver used for C-SKY SMP
|
|
|
|
system.
|
|
|
|
csky,mptimer is not only used in SMP system, it also could be used
|
|
|
|
single core system. It's not a mmio reg and it use mtcr/mfcr instruction.
|
|
|
|
|
2018-11-02 10:51:30 -06:00
|
|
|
config GX6605S_TIMER
|
|
|
|
bool "Gx6605s SOC system timer driver" if COMPILE_TEST
|
|
|
|
depends on CSKY
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
select TIMER_OF
|
|
|
|
help
|
|
|
|
This option enables support for gx6605s SOC's timer.
|
|
|
|
|
2019-02-26 21:53:20 -07:00
|
|
|
config MILBEAUT_TIMER
|
|
|
|
bool "Milbeaut timer driver" if COMPILE_TEST
|
|
|
|
depends on OF
|
|
|
|
depends on ARM
|
|
|
|
select TIMER_OF
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
help
|
|
|
|
Enables the support for Milbeaut timer driver.
|
|
|
|
|
2014-06-16 03:48:45 -06:00
|
|
|
endmenu
|