From: Thara Gopinath <thara.gopinath@linaro.org> To: rui.zhang@intel.com, daniel.lezcano@linaro.org, kvalo@codeaurora.org, davem@davemloft.net, kuba@kernel.org, luciano.coelho@intel.com Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-pm@vger.kernel.org, amitk@kernel.org, nathan.errera@intel.com Subject: [PATCH 2/2] drivers: thermal: Remove thermal_notify_framework Date: Tue, 19 Jan 2021 09:05:41 -0500 [thread overview] Message-ID: <20210119140541.2453490-3-thara.gopinath@linaro.org> (raw) In-Reply-To: <20210119140541.2453490-1-thara.gopinath@linaro.org> thermal_notify_framework just updates for a single trip point where as thermal_zone_device_update does other bookkeeping like updating the temperature of the thermal zone and setting the next trip point. The only driver that was using thermal_notify_framework was updated in the previous patch to use thermal_zone_device_update instead. Since there are no users for thermal_notify_framework remove it. Signed-off-by: Thara Gopinath <thara.gopinath@linaro.org> --- drivers/thermal/thermal_core.c | 18 ------------------ include/linux/thermal.h | 4 ---- 2 files changed, 22 deletions(-) diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c index 4a291d205d5c..04f7581b70c5 100644 --- a/drivers/thermal/thermal_core.c +++ b/drivers/thermal/thermal_core.c @@ -575,24 +575,6 @@ void thermal_zone_device_update(struct thermal_zone_device *tz, } EXPORT_SYMBOL_GPL(thermal_zone_device_update); -/** - * thermal_notify_framework - Sensor drivers use this API to notify framework - * @tz: thermal zone device - * @trip: indicates which trip point has been crossed - * - * This function handles the trip events from sensor drivers. It starts - * throttling the cooling devices according to the policy configured. - * For CRITICAL and HOT trip points, this notifies the respective drivers, - * and does actual throttling for other trip points i.e ACTIVE and PASSIVE. - * The throttling policy is based on the configured platform data; if no - * platform data is provided, this uses the step_wise throttling policy. - */ -void thermal_notify_framework(struct thermal_zone_device *tz, int trip) -{ - handle_thermal_trip(tz, trip); -} -EXPORT_SYMBOL_GPL(thermal_notify_framework); - static void thermal_zone_device_check(struct work_struct *work) { struct thermal_zone_device *tz = container_of(work, struct diff --git a/include/linux/thermal.h b/include/linux/thermal.h index 31b84404f047..77a0b8d060a5 100644 --- a/include/linux/thermal.h +++ b/include/linux/thermal.h @@ -398,7 +398,6 @@ int thermal_zone_get_slope(struct thermal_zone_device *tz); int thermal_zone_get_offset(struct thermal_zone_device *tz); void thermal_cdev_update(struct thermal_cooling_device *); -void thermal_notify_framework(struct thermal_zone_device *, int); int thermal_zone_device_enable(struct thermal_zone_device *tz); int thermal_zone_device_disable(struct thermal_zone_device *tz); void thermal_zone_device_critical(struct thermal_zone_device *tz); @@ -446,9 +445,6 @@ static inline int thermal_zone_get_offset( static inline void thermal_cdev_update(struct thermal_cooling_device *cdev) { } -static inline void thermal_notify_framework(struct thermal_zone_device *tz, - int trip) -{ } static inline int thermal_zone_device_enable(struct thermal_zone_device *tz) { return -ENODEV; } -- 2.25.1
next prev parent reply other threads:[~2021-01-19 23:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-19 14:05 [PATCH 0/2] thermal: Replace thermal_notify_framework with thermal_zone_device_update Thara Gopinath 2021-01-19 14:05 ` [PATCH 1/2] net: wireless: intel: iwlwifi: mvm: tt: Replace thermal_notify_framework Thara Gopinath 2021-01-19 16:19 ` Kalle Valo 2021-01-20 10:46 ` Thara Gopinath 2021-01-19 14:05 ` Thara Gopinath [this message] 2021-01-20 2:56 ` [PATCH 0/2] thermal: Replace thermal_notify_framework with thermal_zone_device_update Zhang, Rui 2021-01-20 10:53 ` Thara Gopinath
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210119140541.2453490-3-thara.gopinath@linaro.org \ --to=thara.gopinath@linaro.org \ --cc=amitk@kernel.org \ --cc=daniel.lezcano@linaro.org \ --cc=davem@davemloft.net \ --cc=kuba@kernel.org \ --cc=kvalo@codeaurora.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=linux-wireless@vger.kernel.org \ --cc=luciano.coelho@intel.com \ --cc=nathan.errera@intel.com \ --cc=netdev@vger.kernel.org \ --cc=rui.zhang@intel.com \ --subject='Re: [PATCH 2/2] drivers: thermal: Remove thermal_notify_framework' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.