diff options
| author | Brian Norris <briannorris@chromium.org> | 2017-03-10 05:46:15 +0300 |
|---|---|---|
| committer | Bjorn Helgaas <bhelgaas@google.com> | 2017-04-21 18:54:35 +0300 |
| commit | 073d3dbe9a7c38888d8dafe09df421b174a6cffa (patch) | |
| tree | a5d31cfbe63c905a5954096b887e70f631a9a2f7 /drivers/thermal/qoriq_thermal.c | |
| parent | 64d6ea602ce619633a6e0af979e2c73738f6aeba (diff) | |
| download | linux-073d3dbe9a7c38888d8dafe09df421b174a6cffa.tar.xz | |
PCI: rockchip: Add remove() support
Currently, if we try to unbind the platform device, the remove will
succeed, but the removal won't undo most of the registration, leaving
partially-configured PCI devices in the system.
This allows, for example, a simple 'lspci' to crash the system, as it will
try to touch the freed (via devm_*) driver structures, e.g., on RK3399:
# echo f8000000.pcie > /sys/bus/platform/drivers/rockchip-pcie/unbind
# lspci
So let's implement device remove().
Signed-off-by: Brian Norris <briannorris@chromium.org>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Acked-by: Shawn Lin <shawn.lin@rock-chips.com>
Diffstat (limited to 'drivers/thermal/qoriq_thermal.c')
0 files changed, 0 insertions, 0 deletions