Skip to content

Commit e5f6e5d

Browse files
baruchsiachbrgl
authored andcommitted
gpio: mvebu: drop pwm base assignment
pwmchip_add() unconditionally assigns the base ID dynamically. Commit f9a8ee8 ("pwm: Always allocate PWM chip base ID dynamically") dropped all base assignment from drivers under drivers/pwm/. It missed this driver. Fix that. Fixes: f9a8ee8 ("pwm: Always allocate PWM chip base ID dynamically") Signed-off-by: Baruch Siach <baruch@tkos.co.il> Reviewed-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Acked-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>
1 parent e75f88e commit e5f6e5d

1 file changed

Lines changed: 0 additions & 7 deletions

File tree

drivers/gpio/gpio-mvebu.c

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -871,13 +871,6 @@ static int mvebu_pwm_probe(struct platform_device *pdev,
871871
mvpwm->chip.dev = dev;
872872
mvpwm->chip.ops = &mvebu_pwm_ops;
873873
mvpwm->chip.npwm = mvchip->chip.ngpio;
874-
/*
875-
* There may already be some PWM allocated, so we can't force
876-
* mvpwm->chip.base to a fixed point like mvchip->chip.base.
877-
* So, we let pwmchip_add() do the numbering and take the next free
878-
* region.
879-
*/
880-
mvpwm->chip.base = -1;
881874

882875
spin_lock_init(&mvpwm->lock);
883876

0 commit comments

Comments
 (0)