diff options
| author | Baruch Siach <[email protected]> | 2022-04-11 09:23:40 +0300 |
|---|---|---|
| committer | Thierry Reding <[email protected]> | 2022-04-22 18:45:51 +0200 |
| commit | eaaad16a9b3f16b411c33404e17d4dc61cf69b16 (patch) | |
| tree | 24ef92581f8766f5db86b5478d6224e53129aa0d | |
| parent | 1d24cc89203081919e339b734728149642786f51 (diff) | |
gpio: mvebu: Drop PWM base assignment
pwmchip_add() unconditionally assigns the base ID dynamically. Commit
f9a8ee8c8bcd1 ("pwm: Always allocate PWM chip base ID dynamically")
dropped all base assignment from drivers under drivers/pwm/. It missed
this driver. Fix that.
Fixes: f9a8ee8c8bcd1 ("pwm: Always allocate PWM chip base ID dynamically")
Signed-off-by: Baruch Siach <[email protected]>
Reviewed-by: Uwe Kleine-König <[email protected]>
Signed-off-by: Thierry Reding <[email protected]>
| -rw-r--r-- | drivers/gpio/gpio-mvebu.c | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/drivers/gpio/gpio-mvebu.c b/drivers/gpio/gpio-mvebu.c index 4c1f9e1091b7..a2c8dd329b31 100644 --- a/drivers/gpio/gpio-mvebu.c +++ b/drivers/gpio/gpio-mvebu.c @@ -871,13 +871,6 @@ static int mvebu_pwm_probe(struct platform_device *pdev, mvpwm->chip.dev = dev; mvpwm->chip.ops = &mvebu_pwm_ops; mvpwm->chip.npwm = mvchip->chip.ngpio; - /* - * There may already be some PWM allocated, so we can't force - * mvpwm->chip.base to a fixed point like mvchip->chip.base. - * So, we let pwmchip_add() do the numbering and take the next free - * region. - */ - mvpwm->chip.base = -1; spin_lock_init(&mvpwm->lock); |