diff options
| author | Vladimir Zapolskiy <vz@mleia.com> | 2023-07-17 17:52:57 +0200 |
|---|---|---|
| committer | Thierry Reding <thierry.reding@gmail.com> | 2023-08-22 10:14:16 +0200 |
| commit | 4aae44f65827f0213a7361cf9c32cfe06114473f (patch) | |
| tree | 921be0afdcb7539eae249e680c3a2333ca7d899d /drivers/staging | |
| parent | b22bb0d6a828b4eab579056647d2f362ac116cf2 (diff) | |
| download | linux-stable-4aae44f65827f0213a7361cf9c32cfe06114473f.tar.gz linux-stable-4aae44f65827f0213a7361cf9c32cfe06114473f.tar.bz2 linux-stable-4aae44f65827f0213a7361cf9c32cfe06114473f.zip | |
pwm: lpc32xx: Remove handling of PWM channels
Because LPC32xx PWM controllers have only a single output which is
registered as the only PWM device/channel per controller, it is known in
advance that pwm->hwpwm value is always 0. On basis of this fact
simplify the code by removing operations with pwm->hwpwm, there is no
controls which require channel number as input.
Even though I wasn't aware at the time when I forward ported that patch,
this fixes a null pointer dereference as lpc32xx->chip.pwms is NULL
before devm_pwmchip_add() is called.
Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Fixes: 3d2813fb17e5 ("pwm: lpc32xx: Don't modify HW state in .probe() after the PWM chip was registered")
Signed-off-by: Thierry Reding <thierry.reding@gmail.com>
Diffstat (limited to 'drivers/staging')
0 files changed, 0 insertions, 0 deletions