clocksource: rework Atmel TCB timer driver
Subsystems (4)
Alexandre Belloni
maintainerv4 cover clocksource: rework Atmel TCB timer driver
Hi,
This series gets back on the TCB drivers rework. It introduces a new driver to handle the clocksource and clockevent devices.
As a reminder, this is necessary because:
- the current tcb_clksrc driver is probed too late to be able to be used at boot and we now have SoCs that don't have a PIT. They currently are not able to boot a mainline kernel.
- using the PIT doesn't work well with preempt-rt because its interrupt is shared (in particular with the UART and their interrupt flags are incompatible)
- the current solution is wasting some TCB channels
The plan is to get this driver upstream, then convert the TCB PWM driver to be able to get rid of the tcb_clksrc driver along with atmel_tclib.
Changes in v4:
- rebased on top of v4.17-rc1
- fixed an issue when setting max_delta for clockevents_config_and_register
Alexandre Belloni (6):
ARM: at91: add TCB registers definitions clocksource/drivers: Add a new driver for the Atmel ARM TC blocks clocksource/drivers: atmel-pit: make option silent
ARM: at91: Implement clocksource selection
ARM: configs: at91: use new TCB timer driver
ARM: configs: at91: unselect PIT
arch/arm/configs/at91_dt_defconfig | 2 +- arch/arm/configs/sama5_defconfig | 2 +- arch/arm/mach-at91/Kconfig | 25 ++ drivers/clocksource/Kconfig | 13 +- drivers/clocksource/Makefile | 3 +- drivers/clocksource/timer-atmel-tcb.c | 608 ++++++++++++++++++++++++++ include/soc/at91/atmel_tcb.h | 216 +++++++++ 7 files changed, 865 insertions(+), 4 deletions(-) create mode 100644 drivers/clocksource/timer-atmel-tcb.c create mode 100644 include/soc/at91/atmel_tcb.h
Signature · 1 line
2.17.0
Alexandre Belloni
maintainerPATCH v4 1/6 ARM: at91: add TCB registers definitions
Add registers and bits definitions for the timer counter blocks found on Atmel ARM SoCs.
--- include/soc/at91/atmel_tcb.h | 216 +++++++++++++++++++++++++++++++++++ 1 file changed, 216 insertions(+) create mode 100644 include/soc/at91/atmel_tcb.h
include/soc/at91/atmel_tcb.h new file +216 -0
@@ -0,0 +1,216 @@ +// SPDX-License-Identifier: GPL-2.0 +/* Copyright (C) 2018 Microchip */ + +#ifndef __SOC_ATMEL_TCB_H +#define __SOC_ATMEL_TCB_H + +/* Channel registers */ +#define ATMEL_TC_COFFS (c) ((c) * 0x40) +#define ATMEL_TC_CCR (c) ATMEL_TC_COFFS(c) +#define ATMEL_TC_CMR (c) (ATMEL_TC_COFFS(c) + 0x4) +#define ATMEL_TC_SMMR (c) (ATMEL_TC_COFFS(c) + 0x8) +#define ATMEL_TC_RAB (c) (ATMEL_TC_COFFS(c) + 0xc) +#define ATMEL_TC_CV (c) (ATMEL_TC_COFFS(c) + 0x10) +#define ATMEL_TC_RA (c) (ATMEL_TC_COFFS(c) + 0x14) +#define ATMEL_TC_RB (c) (ATMEL_TC_COFFS(c) + 0x18) +#define ATMEL_TC_RC (c) (ATMEL_TC_COFFS(c) + 0x1c) +#define ATMEL_TC_SR (c) (ATMEL_TC_COFFS(c) + 0x20) +#define ATMEL_TC_IER (c) (ATMEL_TC_COFFS(c) + 0x24) +#define ATMEL_TC_IDR (c) (ATMEL_TC_COFFS(c) + 0x28) +#define ATMEL_TC_IMR (c) (ATMEL_TC_COFFS(c) + 0x2c) +#define ATMEL_TC_EMR (c) (ATMEL_TC_COFFS(c) + 0x30) + +/* Block registers */ +#define ATMEL_TC_BCR 0xc0 +#define ATMEL_TC_BMR 0xc4 +#define ATMEL_TC_QIER 0xc8 +#define ATMEL_TC_QIDR 0xcc +#define ATMEL_TC_QIMR 0xd0 +#define ATMEL_TC_QISR 0xd4 +#define ATMEL_TC_FMR 0xd8 +#define ATMEL_TC_WPMR 0xe4 + +/* CCR fields */ +#define ATMEL_TC_CCR_CLKEN BIT(0) +#define ATMEL_TC_CCR_CLKDIS BIT(1) +#define ATMEL_TC_CCR_SWTRG BIT(2) + +/* Common CMR fields */ +#define ATMEL_TC_CMR_TCLKS_MSK GENMASK(2, 0) +#define ATMEL_TC_CMR_TCLK (x) (x) +#define ATMEL_TC_CMR_XC (x) ((x) + 5) +#define ATMEL_TC_CMR_CLKI BIT(3) +#define ATMEL_TC_CMR_BURST_MSK GENMASK(5, 4) +#define ATMEL_TC_CMR_BURST_XC (x) (((x) + 1) << 4) +#define ATMEL_TC_CMR_WAVE BIT(15) + +/* Capture mode CMR fields */ +#define ATMEL_TC_CMR_LDBSTOP BIT(6) +#define ATMEL_TC_CMR_LDBDIS BIT(7) +#define ATMEL_TC_CMR_ETRGEDG_MSK GENMASK(9, 8) +#define ATMEL_TC_CMR_ETRGEDG_NONE (0 << 8) +#define ATMEL_TC_CMR_ETRGEDG_RISING (1 << 8) +#define ATMEL_TC_CMR_ETRGEDG_FALLING (2 << 8) +#define ATMEL_TC_CMR_ETRGEDG_BOTH (3 << 8) +#define ATMEL_TC_CMR_ABETRG BIT(10) +#define ATMEL_TC_CMR_CPCTRG BIT(14) +#define ATMEL_TC_CMR_LDRA_MSK GENMASK(17, 16) +#define ATMEL_TC_CMR_LDRA_NONE (0 << 16) +#define ATMEL_TC_CMR_LDRA_RISING (1 << 16) +#define ATMEL_TC_CMR_LDRA_FALLING (2 << 16) +#define ATMEL_TC_CMR_LDRA_BOTH (3 << 16) +#define ATMEL_TC_CMR_LDRB_MSK GENMASK(19, 18) +#define ATMEL_TC_CMR_LDRB_NONE (0 << 18) +#define ATMEL_TC_CMR_LDRB_RISING (1 << 18) +#define ATMEL_TC_CMR_LDRB_FALLING (2 << 18) +#define ATMEL_TC_CMR_LDRB_BOTH (3 << 18) +#define ATMEL_TC_CMR_SBSMPLR_MSK GENMASK(22, 20) +#define ATMEL_TC_CMR_SBSMPLR (x) ((x) << 20) + +/* Waveform mode CMR fields */ +#define ATMEL_TC_CMR_CPCSTOP BIT(6) +#define ATMEL_TC_CMR_CPCDIS BIT(7) +#define ATMEL_TC_CMR_EEVTEDG_MSK GENMASK(9, 8) +#define ATMEL_TC_CMR_EEVTEDG_NONE (0 << 8) +#define ATMEL_TC_CMR_EEVTEDG_RISING (1 << 8) +#define ATMEL_TC_CMR_EEVTEDG_FALLING (2 << 8) +#define ATMEL_TC_CMR_EEVTEDG_BOTH (3 << 8) +#define ATMEL_TC_CMR_EEVT_MSK GENMASK(11, 10) +#define ATMEL_TC_CMR_EEVT_XC (x) (((x) + 1) << 10) +#define ATMEL_TC_CMR_ENETRG BIT(12) +#define ATMEL_TC_CMR_WAVESEL_MSK GENMASK(14, 13) +#define ATMEL_TC_CMR_WAVESEL_UP (0 << 13) +#define ATMEL_TC_CMR_WAVESEL_UPDOWN (1 << 13) +#define ATMEL_TC_CMR_WAVESEL_UPRC (2 << 13) +#define ATMEL_TC_CMR_WAVESEL_UPDOWNRC (3 << 13) +#define ATMEL_TC_CMR_ACPA_MSK GENMASK(17, 16) +#define ATMEL_TC_CMR_ACPA (a) (ATMEL_TC_CMR_ACTION_##a << 16) +#define ATMEL_TC_CMR_ACPC_MSK GENMASK(19, 18) +#define ATMEL_TC_CMR_ACPC (a) (ATMEL_TC_CMR_ACTION_##a << 18) +#define ATMEL_TC_CMR_AEEVT_MSK GENMASK(21, 20) +#define ATMEL_TC_CMR_AEEVT (a) (ATMEL_TC_CMR_ACTION_##a << 20) +#define ATMEL_TC_CMR_ASWTRG_MSK GENMASK(23, 22) +#define ATMEL_TC_CMR_ASWTRG (a) (ATMEL_TC_CMR_ACTION_##a << 22) +#define ATMEL_TC_CMR_BCPB_MSK GENMASK(25, 24) +#define ATMEL_TC_CMR_BCPB (a) (ATMEL_TC_CMR_ACTION_##a << 24) +#define ATMEL_TC_CMR_BCPC_MSK GENMASK(27, 26) +#define ATMEL_TC_CMR_BCPC (a) (ATMEL_TC_CMR_ACTION_##a << 26) +#define ATMEL_TC_CMR_BEEVT_MSK GENMASK(29, 28) +#define ATMEL_TC_CMR_BEEVT (a) (ATMEL_TC_CMR_ACTION_##a << 28) +#define ATMEL_TC_CMR_BSWTRG_MSK GENMASK(31, 30) +#define ATMEL_TC_CMR_BSWTRG (a) (ATMEL_TC_CMR_ACTION_##a << 30) +#define ATMEL_TC_CMR_ACTION_NONE 0 +#define ATMEL_TC_CMR_ACTION_SET 1 +#define ATMEL_TC_CMR_ACTION_CLEAR 2 +#define ATMEL_TC_CMR_ACTION_TOGGLE 3 + +/* SMMR fields */ +#define ATMEL_TC_SMMR_GCEN BIT(0) +#define ATMEL_TC_SMMR_DOWN BIT(1) + +/* SR/IER/IDR/IMR fields */ +#define ATMEL_TC_COVFS BIT(0) +#define ATMEL_TC_LOVRS BIT(1) +#define ATMEL_TC_CPAS BIT(2) +#define ATMEL_TC_CPBS BIT(3) +#define ATMEL_TC_CPCS BIT(4) +#define ATMEL_TC_LDRAS BIT(5) +#define ATMEL_TC_LDRBS BIT(6) +#define ATMEL_TC_ETRGS BIT(7) +#define ATMEL_TC_CLKSTA BIT(16) +#define ATMEL_TC_MTIOA BIT(17) +#define ATMEL_TC_MTIOB BIT(18) + +/* EMR fields */ +#define ATMEL_TC_EMR_TRIGSRCA_MSK GENMASK(1, 0) +#define ATMEL_TC_EMR_TRIGSRCA_TIOA 0 +#define ATMEL_TC_EMR_TRIGSRCA_PWMX 1 +#define ATMEL_TC_EMR_TRIGSRCB_MSK GENMASK(5, 4) +#define ATMEL_TC_EMR_TRIGSRCB_TIOB (0 << 4) +#define ATMEL_TC_EMR_TRIGSRCB_PWM (1 << 4) +#define ATMEL_TC_EMR_NOCLKDIV BIT(8) + +/* BCR fields */ +#define ATMEL_TC_BCR_SYNC BIT(0) + +/* BMR fields */ +#define ATMEL_TC_BMR_TCXC_MSK (c) GENMASK(((c) * 2) + 1, (c) * 2) +#define ATMEL_TC_BMR_TCXC (x, c) ((x) << (2 * (c))) +#define ATMEL_TC_BMR_QDEN BIT(8) +#define ATMEL_TC_BMR_POSEN BIT(9) +#define ATMEL_TC_BMR_SPEEDEN BIT(10) +#define ATMEL_TC_BMR_QDTRANS BIT(11) +#define ATMEL_TC_BMR_EDGPHA BIT(12) +#define ATMEL_TC_BMR_INVA BIT(13) +#define ATMEL_TC_BMR_INVB BIT(14) +#define ATMEL_TC_BMR_INVIDX BIT(15) +#define ATMEL_TC_BMR_SWAP BIT(16) +#define ATMEL_TC_BMR_IDXPHB BIT(17) +#define ATMEL_TC_BMR_AUTOC BIT(18) +#define ATMEL_TC_MAXFILT_MSK GENMASK(25, 20) +#define ATMEL_TC_MAXFILT (x) (((x) - 1) << 20) +#define ATMEL_TC_MAXCMP_MSK GENMASK(29, 26) +#define ATMEL_TC_MAXCMP (x) ((x) << 26) + +/* QEDC fields */ +#define ATMEL_TC_QEDC_IDX BIT(0) +#define ATMEL_TC_QEDC_DIRCHG BIT(1) +#define ATMEL_TC_QEDC_QERR BIT(2) +#define ATMEL_TC_QEDC_MPE BIT(3) +#define ATMEL_TC_QEDC_DIR BIT(8) + +/* FMR fields */ +#define ATMEL_TC_FMR_ENCF (x) BIT(x) + +/* WPMR fields */ +#define ATMEL_TC_WPMR_WPKEY (0x54494d << 8) +#define ATMEL_TC_WPMR_WPEN BIT(0) + +static inline struct clk *tcb_clk_get (struct device_node *node,int channel) +{ +struct clk *clk; +char clk_name[] ="t0_clk" ; + + clk_name[1 ] += channel; + clk =of_clk_get_by_name (node->parent, clk_name); +if (!IS_ERR (clk)) +return clk; + +return of_clk_get_by_name (node->parent,"t0_clk" ); +} + +static inline int tcb_irq_get (struct device_node *node,int channel) +{ +int irq; + + irq =of_irq_get (node->parent, channel); +if (irq >0 ) +return irq; + +return of_irq_get (node->parent,0 ); +} + +static const u8 atmel_tc_divisors[5 ] = {2 ,8 ,32 ,128 ,0 , }; + +struct atmel_tcb_info { +int bits; +}; + +static const struct atmel_tcb_info atmel_tcb_infos[] = { + { .bits =16 }, + { .bits =32 }, +}; + +static const struct of_device_id atmel_tcb_dt_ids[] = { + { + .compatible ="atmel,at91rm9200-tcb" , + .data = &atmel_tcb_infos[0 ], + }, { + .compatible ="atmel,at91sam9x5-tcb" , + .data = &atmel_tcb_infos[1 ], + }, { +/* sentinel */ + } +}; + +#endif /* __SOC_ATMEL_TCB_H */
Signature · 1 line
2.17.0
Re: [PATCH v4 1/6] ARM: at91: add TCB registers definitions
include/soc/at91/atmel_tcb.h
Quoted 5 lines · Alexandre Belloni
include/soc/at91/atmel_tcb.h new file +0
-0
?
Quoted 36 lines
include/soc/at91/atmel_tcb.h new file +36
-0+static inline struct clk *tcb_clk_get (struct device_node *node,int channel) +{ +struct clk *clk; +char clk_name[] ="t0_clk" ; + + clk_name[1 ] += channel; + clk =of_clk_get_by_name (node->parent, clk_name); +if (!IS_ERR (clk)) +return clk; + +return of_clk_get_by_name (node->parent,"t0_clk" ); +} + +static inline int tcb_irq_get (struct device_node *node,int channel) +{ +int irq; + + irq =of_irq_get (node->parent, channel); +if (irq >0 ) +return irq; + +return of_irq_get (node->parent,0 ); +} + +static const u8 atmel_tc_divisors[5 ] = {2 ,8 ,32 ,128 ,0 , }; + +struct atmel_tcb_info { +int bits; +}; + +static const struct atmel_tcb_info atmel_tcb_infos[] = { + { .bits =16 }, + { .bits =32 }, +}; + +static const struct of_device_id atmel_tcb_dt_ids[] = {
include/soc/at91/atmel_tcb.h line 214
Quoted 10 lines
include/soc/at91/atmel_tcb.h new file +10
-0+ { + .compatible = "atmel,at91rm9200-tcb", + .data = &atmel_tcb_infos[0], + }, { + .compatible = "atmel,at91sam9x5-tcb", + .data = &atmel_tcb_infos[1], + }, { +/* sentinel */ + } +};
After the series is applied, I see only one user of that file. The data structures don't look like they belong here. Same goes for the static inline of the code above.
Quoted 1 line
+#endif /*
__SOC_ATMEL_TCB_H*/
Sebastian
Alexandre Belloni
maintainerRe: [PATCH v4 1/6] ARM: at91: add TCB registers definitions
Quoted 49 lines · Sebastian Andrzej Siewior
include/soc/at91/atmel_tcb.h
Quoted 5 lines · Alexandre Belloni
include/soc/at91/atmel_tcb.h new file +0
-0?
Quoted 42 lines
include/soc/at91/atmel_tcb.h new file +42
-0+static inline struct clk *tcb_clk_get (struct device_node *node,int channel) +{ +struct clk *clk; +char clk_name[] ="t0_clk" ; + + clk_name[1 ] += channel; + clk =of_clk_get_by_name (node->parent, clk_name); +if (!IS_ERR (clk)) +return clk; + +return of_clk_get_by_name (node->parent,"t0_clk" ); +} + +static inline int tcb_irq_get (struct device_node *node,int channel) +{ +int irq; + + irq =of_irq_get (node->parent, channel); +if (irq >0 ) +return irq; + +return of_irq_get (node->parent,0 ); +} + +static const u8 atmel_tc_divisors[5 ] = {2 ,8 ,32 ,128 ,0 , }; + +struct atmel_tcb_info { +int bits; +}; + +static const struct atmel_tcb_info atmel_tcb_infos[] = { + { .bits =16 }, + { .bits =32 }, +}; + +static const struct of_device_id atmel_tcb_dt_ids[] = { + { + .compatible ="atmel,at91rm9200-tcb" , + .data = &atmel_tcb_infos[0 ], + }, { + .compatible ="atmel,at91sam9x5-tcb" , + .data = &atmel_tcb_infos[1 ],
Quoted 9 lines
include/soc/at91/atmel_tcb.h line 214
Quoted 4 lines
include/soc/at91/atmel_tcb.h new file +4
-0+ }, { +/* sentinel */ + } +};After the series is applied, I see only one user of that file. The data structures don't look like they belong here. Same goes for the static inline of the code above.
There is another user coming later (the pwm driver) but I didn't repost, I'll do so after this series is applied.
Quoted 3 lines
Quoted 1 line
+#endif /*
__SOC_ATMEL_TCB_H*/Sebastian
Signature · 3 lines
Alexandre Belloni, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com
Alexandre Belloni
maintainerPATCH v4 2/6 clocksource/drivers: Add a new driver for the Atmel ARM TC blocks
In reply to Alexandre BelloniAdd a driver for the Atmel Timer Counter Blocks. This driver provides a clocksource and two clockevent devices.
One of the clockevent device is linked to the clocksource counter and so it will run at the same frequency. This will be used when there is only on TCB channel available for timers.
The other clockevent device runs on a separate TCB channel when available.
This driver uses regmap and syscon to be able to probe early in the boot and avoid having to switch on the TCB clocksource later. Using regmap also means that unused TCB channels may be used by other drivers (PWM for example). read/writel are still used to access channel specific registers to avoid the performance impact of regmap (mainly locking).
--- drivers/clocksource/Kconfig | 8 + drivers/clocksource/Makefile | 3 +- drivers/clocksource/timer-atmel-tcb.c | 608 ++++++++++++++++++++++++++ 3 files changed, 618 insertions(+), 1 deletion(-) create mode 100644 drivers/clocksource/timer-atmel-tcb.c
drivers/clocksource/Kconfig +8 -0
@@ -395,6 +395,14 @@ config ATMEL_ST help Support for the Atmel ST timer. +config ATMEL_ARM_TCB_CLKSRC + bool "Microchip ARM TC Block" if COMPILE_TEST + select REGMAP_MMIO + depends on GENERIC_CLOCKEVENTS + help + This enables build of clocksource and clockevent driver for + the integrated Timer Counter Blocks in Microchip ARM SoCs. + config CLKSRC_EXYNOS_MCT bool "Exynos multi core timer driver" if COMPILE_TEST depends on ARM || ARM64
drivers/clocksource/Makefile +2 -1
@@ -3,7 +3,8 @@ obj-$(CONFIG_TIMER_OF) += timer-of.o obj-$(CONFIG_TIMER_PROBE) += timer-probe.o obj-$(CONFIG_ATMEL_PIT) += timer-atmel-pit.o obj-$(CONFIG_ATMEL_ST) += timer-atmel-st.o -obj-$(CONFIG_ATMEL_TCB_CLKSRC) += tcb_clksrc.o +obj-$(CONFIG_ATMEL_TCB_CLKSRC) += tcb_clksrc.o +obj-$(CONFIG_ATMEL_ARM_TCB_CLKSRC) += timer-atmel-tcb.o obj-$(CONFIG_X86_PM_TIMER) += acpi_pm.o obj-$(CONFIG_SCx200HR_TIMER) += scx200_hrt.o obj-$(CONFIG_CS5535_CLOCK_EVENT_SRC) += cs5535-clockevt.o
drivers/clocksource/timer-atmel-tcb.c new file +608 -0
608 lines not on this page · raw message
Signature · 1 line
2.17.0
Alexandre Belloni
maintainerPATCH v4 3/6 clocksource/drivers: atmel-pit: make option silent
In reply to Alexandre BelloniTo conform with the other option, make the ATMEL_PIT option silent so it can be selected from the platform
--- drivers/clocksource/Kconfig | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/clocksource/Kconfig +4 -1
@@ -384,8 +384,11 @@ config ARMV7M_SYSTICK This options enables support for the ARMv7M system timer unit config ATMEL_PIT + bool "Microchip ARM Periodic Interval Timer (PIT)" if COMPILE_TEST select TIMER_OF if OF - def_bool SOC_AT91SAM9 || SOC_SAMA5 + help + This enables build of clocksource and clockevent driver for + the integrated PIT in Microchip ARM SoCs. config ATMEL_ST bool "Atmel ST timer support" if COMPILE_TEST
Signature · 1 line
2.17.0
Alexandre Belloni
maintainerPATCH v4 4/6 ARM: at91: Implement clocksource selection
In reply to Alexandre BelloniAllow selecting and unselecting the PIT clocksource driver so it doesn't have to be compile when unused.
--- arch/arm/mach-at91/Kconfig | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+)
arch/arm/mach-at91/Kconfig +25 -0
@@ -106,6 +106,31 @@ config SOC_AT91SAM9 AT91SAM9X35 AT91SAM9XE +comment "Clocksource driver selection" + +config ATMEL_CLOCKSOURCE_PIT + bool "Periodic Interval Timer (PIT) support" + depends on SOC_AT91SAM9 || SOC_SAMA5 + default SOC_AT91SAM9 || SOC_SAMA5 + select ATMEL_PIT + help + Select this to get a clocksource based on the Atmel Periodic Interval + Timer. It has a relatively low resolution and the TC Block clocksource + should be preferred. + +config ATMEL_CLOCKSOURCE_TCB + bool "Timer Counter Blocks (TCB) support" + depends on SOC_AT91RM9200 || SOC_AT91SAM9 || SOC_SAMA5 || COMPILE_TEST + default SOC_AT91RM9200 || SOC_AT91SAM9 || SOC_SAMA5 + depends on !ATMEL_TCLIB + select ATMEL_ARM_TCB_CLKSRC + help + Select this to get a high precision clocksource based on a + TC block with a 5+ MHz base clock rate. + On platforms with 16-bit counters, two timer channels are combined + to make a single 32-bit timer. + It can also be used as a clock event device supporting oneshot mode. + config HAVE_AT91_UTMI bool
Signature · 1 line
2.17.0
Alexandre Belloni
maintainerPATCH v4 5/6 ARM: configs: at91: use new TCB timer driver
In reply to Alexandre BelloniUnselecting ATMEL_TCLIB switches the TCB timer driver from tcb_clksrc to timer-atmel-tcb.
--- arch/arm/configs/at91_dt_defconfig | 1 - arch/arm/configs/sama5_defconfig | 1 - 2 files changed, 2 deletions(-)
arch/arm/configs/at91_dt_defconfig +0 -1
@@ -64,7 +64,6 @@ CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=4 CONFIG_BLK_DEV_RAM_SIZE=8192 -CONFIG_ATMEL_TCLIB=y CONFIG_ATMEL_SSC=y CONFIG_SCSI=y CONFIG_BLK_DEV_SD=y
arch/arm/configs/sama5_defconfig +0 -1
@@ -75,7 +75,6 @@ CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=4 CONFIG_BLK_DEV_RAM_SIZE=8192 -CONFIG_ATMEL_TCLIB=y CONFIG_ATMEL_SSC=y CONFIG_EEPROM_AT24=y CONFIG_SCSI=y
Signature · 1 line
2.17.0
Alexandre Belloni
maintainerPATCH v4 6/6 ARM: configs: at91: unselect PIT
In reply to Alexandre BelloniThe PIT is not required anymore to successfully boot and may actually harm in case preempt-rt is used because the PIT interrupt is shared. Disable it so the TCB clocksource is used.
--- arch/arm/configs/at91_dt_defconfig | 1 + arch/arm/configs/sama5_defconfig | 1 + 2 files changed, 2 insertions(+)
arch/arm/configs/at91_dt_defconfig +1 -0
@@ -19,6 +19,7 @@ CONFIG_ARCH_MULTI_V5=y CONFIG_ARCH_AT91=y CONFIG_SOC_AT91RM9200=y CONFIG_SOC_AT91SAM9=y +# CONFIG_ATMEL_CLOCKSOURCE_PIT is not set CONFIG_AEABI=y CONFIG_UACCESS_WITH_MEMCPY=y CONFIG_ZBOOT_ROM_TEXT=0x0
arch/arm/configs/sama5_defconfig +1 -0
@@ -20,6 +20,7 @@ CONFIG_ARCH_AT91=y CONFIG_SOC_SAMA5D2=y CONFIG_SOC_SAMA5D3=y CONFIG_SOC_SAMA5D4=y +# CONFIG_ATMEL_CLOCKSOURCE_PIT is not set CONFIG_AEABI=y CONFIG_UACCESS_WITH_MEMCPY=y CONFIG_ZBOOT_ROM_TEXT=0x0
Signature · 1 line
2.17.0
Quoted 1 line · Alexandre Belloni
Hi,
Hi,
please keep on Cc if you intend to repost this.
Quoted 2 lines
This series gets back on the TCB drivers rework. It introduces a new driver to handle the clocksource and clockevent devices.
So you don't want the old thing we have in -RT. I remember you (the atmel folks) wanted something different the last time I posted the patches.
Quoted 7 lines
As a reminder, this is necessary because:
- the currenttcb_clksrcdriver is probed too late to be able to be used at boot and we now have SoCs that don't have a PIT. They currently are not able to boot a mainline kernel.
- using the PIT doesn't work well with preempt-rt because its interrupt is shared (in particular with the UART and their interrupt flags are incompatible)
If you could get rid of this:
| clocksource: Switched to clocksource timer at f0010000:0 | BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:974 | in_atomic(): 1, irqs_disabled(): 128, pid: 1, name: swapper | Preemption disabled at: | [<c014f7ac>] __handle_domain_irq+0x40/0xdc | Hardware name: Atmel SAMA5 | [<c010e14c>] (unwind_backtrace) from [<c010bd74>] (show_stack+0x10/0x14) | [<c010bd74>] (show_stack) from [<c013b314>] (___might_sleep+0x16c/0x1c0) | [<c013b314>] (___might_sleep) from [<c06696f0>] (rt_spin_lock+0x40/0x80) | [<c06696f0>] (rt_spin_lock) from [<c046e030>] (clk_enable_lock+0x30/0xe4) | [<c046e030>] (clk_enable_lock) from [<c046ea4c>] (clk_core_disable_lock+0xc/0x1c) | [<c046ea4c>] (clk_core_disable_lock) from [<c059d07c>] (tc_clkevt2_shutdown+0x64/0x6c) | [<c059d07c>] (tc_clkevt2_shutdown) from [<c059d09c>] (tc_clkevt2_set_oneshot+0x18/0x78) | [<c059d09c>] (tc_clkevt2_set_oneshot) from [<c0172a00>] (clockevents_switch_state+0xb8/0x130) | [<c0172a00>] (clockevents_switch_state) from [<c0173a60>] (tick_switch_to_oneshot+0x48/0xb8) | [<c0173a60>] (tick_switch_to_oneshot) from [<c0165a0c>] (hrtimer_run_queues+0xf0/0x15c) | [<c0165a0c>] (hrtimer_run_queues) from [<c0164010>] (run_local_timers+0x8/0x38) | [<c0164010>] (run_local_timers) from [<c0164070>] (update_process_times+0x30/0x60) | [<c0164070>] (update_process_times) from [<c0173008>] (tick_handle_periodic+0x1c/0x90) | [<c0173008>] (tick_handle_periodic) from [<c059c954>] (tc_clkevt2_irq+0x38/0x48) | [<c059c954>] (tc_clkevt2_irq) from [<c014fe6c>] (__handle_irq_event_percpu+0x7c/0x28c)
that would be so awesome.
Quoted 4 lines
- the current solution is wasting some TCB channels
The plan is to get this driver upstream, then convert the TCB PWM driver to be able to get rid of the
tcb_clksrcdriver along withatmel_tclib.
The config options are now less than optimal (for me at least). On oldconfig it asks you for PIT and I say selected no because I wanted the new one. So I end up with nothing.
Not sure you want do something about it?
Is the resolution more or the same compared what we have in -RT? On an idle system this clocks goes up to 180us/ 190us while the old clock started at 160us and moved to around 180us after one hackbench invocation. This could be nothing, it could be a lower frequency of the clockevents device.
If you intend to stick with this driver then I would replace the current hack in -RT with this series.
Sebastian
Alexandre Belloni
maintainerQuoted 7 lines · Sebastian Andrzej Siewior
Quoted 1 line · Alexandre Belloni
Hi,
Hi,
please keep on Cc if you intend to repost this.
Sure, I'll do.
Quoted 7 lines
Quoted 2 lines
This series gets back on the TCB drivers rework. It introduces a new driver to handle the clocksource and clockevent devices.
So you don't want the old thing we have in -RT. I remember you (the atmel folks) wanted something different the last time I posted the patches.
I don't remember you posted anything for the TCB. Wasn't it focused on getting rid of the PIT irq?
As said below, this is solving multiple issues, including the one for SoCs that don't have the PIT.
Quoted 31 lines
Quoted 7 lines
As a reminder, this is necessary because:
- the currenttcb_clksrcdriver is probed too late to be able to be used at boot and we now have SoCs that don't have a PIT. They currently are not able to boot a mainline kernel.
- using the PIT doesn't work well with preempt-rt because its interrupt is shared (in particular with the UART and their interrupt flags are incompatible)If you could get rid of this:
| clocksource: Switched to clocksource timer at f0010000:0 | BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:974 | in_atomic(): 1, irqs_disabled(): 128, pid: 1, name: swapper | Preemption disabled at: | [<c014f7ac>] __handle_domain_irq+0x40/0xdc | Hardware name: Atmel SAMA5 | [<c010e14c>] (unwind_backtrace) from [<c010bd74>] (show_stack+0x10/0x14) | [<c010bd74>] (show_stack) from [<c013b314>] (___might_sleep+0x16c/0x1c0) | [<c013b314>] (___might_sleep) from [<c06696f0>] (rt_spin_lock+0x40/0x80) | [<c06696f0>] (rt_spin_lock) from [<c046e030>] (clk_enable_lock+0x30/0xe4) | [<c046e030>] (clk_enable_lock) from [<c046ea4c>] (clk_core_disable_lock+0xc/0x1c) | [<c046ea4c>] (clk_core_disable_lock) from [<c059d07c>] (tc_clkevt2_shutdown+0x64/0x6c) | [<c059d07c>] (tc_clkevt2_shutdown) from [<c059d09c>] (tc_clkevt2_set_oneshot+0x18/0x78) | [<c059d09c>] (tc_clkevt2_set_oneshot) from [<c0172a00>] (clockevents_switch_state+0xb8/0x130) | [<c0172a00>] (clockevents_switch_state) from [<c0173a60>] (tick_switch_to_oneshot+0x48/0xb8) | [<c0173a60>] (tick_switch_to_oneshot) from [<c0165a0c>] (hrtimer_run_queues+0xf0/0x15c) | [<c0165a0c>] (hrtimer_run_queues) from [<c0164010>] (run_local_timers+0x8/0x38) | [<c0164010>] (run_local_timers) from [<c0164070>] (update_process_times+0x30/0x60) | [<c0164070>] (update_process_times) from [<c0173008>] (tick_handle_periodic+0x1c/0x90) | [<c0173008>] (tick_handle_periodic) from [<c059c954>] (tc_clkevt2_irq+0x38/0x48) | [<c059c954>] (tc_clkevt2_irq) from [<c014fe6c>] (__handle_irq_event_percpu+0x7c/0x28c)
Quoted 2 lines
that would be so awesome.
Ok, if I understand correctly tc_clkevt2_set_oneshot is called from atomic context so it shouldn't call tc_clkevt2_shutdown.
Back in 2016, tglx said:
"There was an earlier discussion about the clk stuff. Actually the lock protecting disable/enable should be made raw, but there was some crap going on in some of the clk callbacks which made that impossible. We realy should revisit this."
Anyway, I'll try to avoid disabling the clock just to reenable it afterwards.
(Actually, I've just checked before sending and I've found your patch, I'll do something similar)
Quoted 10 lines
Quoted 4 lines
- the current solution is wasting some TCB channels
The plan is to get this driver upstream, then convert the TCB PWM driver to be able to get rid of the
tcb_clksrcdriver along withatmel_tclib.The config options are now less than optimal (for me at least). On oldconfig it asks you for PIT and I say selected no because I wanted the new one. So I end up with nothing.
Not sure you want do something about it?
I don't think you ending up with nothing but probably you removed the PIT and kept ATMEL_TCLIB which is the combination that is really difficult to protect from. I don't think it is worth the added Kconfig complexity.
Quoted 6 lines
Is the resolution more or the same compared what we have in -RT? On an idle system this clocks goes up to 180us/ 190us while the old clock started at 160us and moved to around 180us after one hackbench invocation. This could be nothing, it could be a lower frequency of the clockevents device.
The driver shouldn't change anything on that side.
Quoted 3 lines
If you intend to stick with this driver then I would replace the current hack in -RT with this series.
That is one of the goal, yes.
The remaining one would be "clocksource: TCLIB: Allow higher clock rates for clock events"
Signature · 3 lines
Alexandre Belloni, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com
Quoted 3 lines · Alexandre Belloni
I don't remember you posted anything for the TCB. Wasn't it focused on getting rid of the PIT irq?
the PIT irq which was shared with the UART one some devices, yes this was part of it. The other essential piece was using a higher frequency for the device:
https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/tree/patches/clocksource-tclib-allow-higher-clockrates.patch?h=linux-4.14.y-rt-patches
Quoted 2 lines
As said below, this is solving multiple issues, including the one for SoCs that don't have the PIT.
will the PIT be removed? Where it needs the PIT?
Quoted 9 lines
Ok, if I understand correctly
tc_clkevt2_set_oneshotis called from atomic context so it shouldn't calltc_clkevt2_shutdown.Back in 2016, tglx said:
"There was an earlier discussion about the clk stuff. Actually the lock protecting disable/enable should be made raw, but there was some crap going on in some of the clk callbacks which made that impossible. We realy should revisit this."
Quoted 5 lines
Anyway, I'll try to avoid disabling the clock just to reenable it afterwards.
(Actually, I've just checked before sending and I've found your patch, I'll do something similar)
thanks.
Quoted 11 lines
Quoted 10 lines
Quoted 4 lines
- the current solution is wasting some TCB channels
The plan is to get this driver upstream, then convert the TCB PWM driver to be able to get rid of the
tcb_clksrcdriver along withatmel_tclib.The config options are now less than optimal (for me at least). On oldconfig it asks you for PIT and I say selected no because I wanted the new one. So I end up with nothing.
Not sure you want do something about it?
Quoted 4 lines
I don't think you ending up with nothing but probably you removed the PIT and kept
ATMEL_TCLIBwhich is the combination that is really difficult to protect from. I don't think it is worth the addedKconfigcomplexity.
TCLIB was still enabled yes. It is 'oldconfig'.
Quoted 9 lines
Quoted 6 lines
Is the resolution more or the same compared what we have in -RT? On an idle system this clocks goes up to 180us/ 190us while the old clock started at 160us and moved to around 180us after one hackbench invocation. This could be nothing, it could be a lower frequency of the clockevents device.
The driver shouldn't change anything on that side.
Quoted 8 lines
Quoted 3 lines
If you intend to stick with this driver then I would replace the current hack in -RT with this series.
That is one of the goal, yes.
The remaining one would be "clocksource: TCLIB: Allow higher clock rates for clock events"
I see. So I would need to keep that patch in queue after it was dismissed from duty?
Sebastian
Alexandre Belloni
maintainerQuoted 5 lines · Sebastian Andrzej Siewior
Quoted 3 lines · Alexandre Belloni
I don't remember you posted anything for the TCB. Wasn't it focused on getting rid of the PIT irq?
Quoted 9 lines
the PIT irq which was shared with the UART one some devices, yes this was part of it. The other essential piece was using a higher frequency for the device:
https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/tree/patches/clocksource-tclib-allow-higher-clockrates.patch?h=linux-4.14.y-rt-patchesQuoted 2 lines
As said below, this is solving multiple issues, including the one for SoCs that don't have the PIT.
will the PIT be removed? Where it needs the PIT?
The last patch is unselecting the PIT driver so by default it is not enabled. The PIT driver will stay just in case someone has to use it e.g. when they are using all the TCB channels for something else. However, recent Atmel SoC have a TCB without any output so it can ony be used as a timer. Some other SoCs don't have a PIT at all.
Quoted 7 lines
Quoted 4 lines
I don't think you ending up with nothing but probably you removed the PIT and kept
ATMEL_TCLIBwhich is the combination that is really difficult to protect from. I don't think it is worth the addedKconfigcomplexity.TCLIB was still enabled yes. It is 'oldconfig'.
Hum, ok, I'll try to provide a cleaner path.
Quoted 5 lines
Quoted 2 lines
The remaining one would be "clocksource: TCLIB: Allow higher clock rates for clock events"
I see. So I would need to keep that patch in queue after it was dismissed from duty?
Boris suggested a DT binding to allow changing the rate but it didn't reach consensus at the time. this is something that will ne to be revived at some point and I would very much like having that upstream too.
Signature · 3 lines
Alexandre Belloni, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com
Quoted 10 lines · Alexandre Belloni
Quoted 4 lines
Quoted 2 lines
As said below, this is solving multiple issues, including the one for SoCs that don't have the PIT.
will the PIT be removed? Where it needs the PIT?
The last patch is unselecting the PIT driver so by default it is not enabled. The PIT driver will stay just in case someone has to use it e.g. when they are using all the TCB channels for something else. However, recent Atmel SoC have a TCB without any output so it can ony be used as a timer. Some other SoCs don't have a PIT at all.
The question was more "does it make sense to keep the 'old' PIT driver around or can it be removed and the TCB driver will be used by everyone"?
Quoted 10 lines
Quoted 5 lines
Quoted 2 lines
The remaining one would be "clocksource: TCLIB: Allow higher clock rates for clock events"
I see. So I would need to keep that patch in queue after it was dismissed from duty?
Boris suggested a DT binding to allow changing the rate but it didn't reach consensus at the time. this is something that will ne to be revived at some point and I would very much like having that upstream too.
Does make sense to have a low frequency clock here? I think from clocksource point of view it makes sense to have it (highres) enabled and not having to adjust the DT first (not to mention to learn about it).
Sebastian