Commit 4917e498 authored by Fabrice Gasnier's avatar Fabrice Gasnier Committed by Lee Jones

mfd: stm32-timers: Avoid clearing auto reload register

The ARR register is cleared unconditionally upon probing, after the maximum
value has been read. This initial condition is rather not intuitive, when
considering the counter child driver. It rather expects the maximum value
by default:
- The counter interface shows a zero value by default for 'ceiling'
  attribute.
- Enabling the counter without any prior configuration makes it doesn't
  count.

The reset value of ARR register is the maximum. So Choice here
is to backup it, and restore it then, instead of clearing its value.
It also fixes the initial condition seen by the counter driver.

Fixes: d0f949e2 ("mfd: Add STM32 Timers driver")
Signed-off-by: default avatarFabrice Gasnier <fabrice.gasnier@foss.st.com>
Acked-by: default avatarWilliam Breathitt Gray <vilhelm.gray@gmail.com>
Signed-off-by: default avatarLee Jones <lee.jones@linaro.org>
parent 10d82ade
...@@ -158,13 +158,18 @@ static const struct regmap_config stm32_timers_regmap_cfg = { ...@@ -158,13 +158,18 @@ static const struct regmap_config stm32_timers_regmap_cfg = {
static void stm32_timers_get_arr_size(struct stm32_timers *ddata) static void stm32_timers_get_arr_size(struct stm32_timers *ddata)
{ {
u32 arr;
/* Backup ARR to restore it after getting the maximum value */
regmap_read(ddata->regmap, TIM_ARR, &arr);
/* /*
* Only the available bits will be written so when readback * Only the available bits will be written so when readback
* we get the maximum value of auto reload register * we get the maximum value of auto reload register
*/ */
regmap_write(ddata->regmap, TIM_ARR, ~0L); regmap_write(ddata->regmap, TIM_ARR, ~0L);
regmap_read(ddata->regmap, TIM_ARR, &ddata->max_arr); regmap_read(ddata->regmap, TIM_ARR, &ddata->max_arr);
regmap_write(ddata->regmap, TIM_ARR, 0x0); regmap_write(ddata->regmap, TIM_ARR, arr);
} }
static int stm32_timers_dma_probe(struct device *dev, static int stm32_timers_dma_probe(struct device *dev,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment