diff options
| author | Uwe Kleine-König <[email protected]> | 2022-06-21 08:40:36 +0200 |
|---|---|---|
| committer | Bartosz Golaszewski <[email protected]> | 2022-06-23 16:42:27 +0200 |
| commit | c1c2a15c2b5379ea8e44dcdcc298e3de42076ba0 (patch) | |
| tree | c3f483f65ccb9dbe9204dfc13cc3f415f0486e9f /include/linux/fpga/fpga-mgr.h | |
| parent | 9ca766eaea2e87b8b773bff04ee56c055cb76d4e (diff) | |
gpio: grgpio: Fix device removing
If a platform device's remove callback returns non-zero, the device core
emits a warning and still removes the device and calls the devm cleanup
callbacks.
So it's not save to not unregister the gpiochip because on the next request
to a GPIO the driver accesses kfree()'d memory. Also if an IRQ triggers,
the freed memory is accessed.
Instead rely on the GPIO framework to ensure that after gpiochip_remove()
all GPIOs are freed and so the corresponding IRQs are unmapped.
This is a preparation for making platform remove callbacks return void.
Signed-off-by: Uwe Kleine-König <[email protected]>
Reviewed-by: Andy Shevchenko <[email protected]>
Signed-off-by: Bartosz Golaszewski <[email protected]>
Diffstat (limited to 'include/linux/fpga/fpga-mgr.h')
0 files changed, 0 insertions, 0 deletions