thermal: core: Remove thermal zones during unregistration
Get series with b4
b4 am 1880915.tdWV9SEqCh@kreacherVersions newest first
- v1 Latest3 patches 10 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | thermal: core: Make thermal_zone_device_unregister() return after freeing the zonedrivers/ include/ | +7 | 4 replies | |
| 2/3 | thermal: Drop redundant and confusing device_is_registered() checksdrivers/ drivers/ drivers/ +1 more | +7 | 3 replies | |
| 3/3 | thermal: core: Rework thermal zone availability checkdrivers/ | +12 | 1 reply |
Reviews trailers per patch
All 3 patches have a Reviewed-by or Acked-by.
| Patch | Lukasz Luba | Daniel Lezcano |
|---|---|---|
| Series | Reviewed-and-tested-by | |
| 1/3 | A-b | |
| 2/3 | A-b | |
| 3/3 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v1 0/3] thermal: core: Remove thermal zones during unregistration
Hi All,
This patch series adds a mechanism to guarantee that thermal_zone_device_unregister() will not return until all of the active references to the thermal zone device object in question have been dropped and it has been deleted (patch [1/3]).
This supersedes the approach used so far in which all thermal zone sysfs attribute callbacks check if the zone device is still registered under the zone lock, so as to return early if that is not the case, as it means that device_del() has been called for the thermal zone in question (and returned). It is not necessary to do that any more after patch [1/3], so patch [2/3] removes those checks from the code and drops zone locking that is not necessary any more either.
Patch [3/3] uses the observation that the thermal subsystem does not need to check if a thermal zone device is registered at all, because it can use its own data to determine whether or not the thermal zone is going away and so it may not be worth updating it, for example.
Please refer to the patch changelogs for details.
The series depends on new thermal material in linux-next, but it should not substantially depend on any changes that have not made it into linux-next yet.
Thanks!