From: Keerthy <j-keerthy@ti.com>
To: <rui.zhang@intel.com>, <edubezval@gmail.com>
Cc: <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <nm@ti.com>, <t-kristo@ti.com>
Subject: Re: [PATCH v6 1/2] thermal: core: Allow orderly_poweroff to be called only once
Date: Tue, 2 May 2017 09:10:01 +0530 [thread overview]
Message-ID: <5a3df459-0fd7-e042-7e1d-fd76e7652e09@ti.com> (raw)
In-Reply-To: <1492489799-6452-1-git-send-email-j-keerthy@ti.com>
On Tuesday 18 April 2017 09:59 AM, Keerthy wrote:
> thermal_zone_device_check --> thermal_zone_device_update -->
> handle_thermal_trip --> handle_critical_trips --> orderly_poweroff
>
> The above sequence happens every 250/500 mS based on the configuration.
> The orderly_poweroff function is getting called every 250/500 mS.
> With a full fledged file system it takes at least 5-10 Seconds to
> power off gracefully.
>
> In that period due to the thermal_zone_device_check triggering
> periodically the thermal work queues bombard with
> orderly_poweroff calls multiple times eventually leading to
> failures in gracefully powering off the system.
>
> Make sure that orderly_poweroff is called only once.
>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> Acked-by: Eduardo Valentin <edubezval@gmail.com>
Zhang,
Could you pull this?
- Keerthy
> ---
>
> Changes in v5:
>
> * Added Eduardo's Ack.
>
> Changes in v4:
>
> * power_off_triggered declaration together with mutex definition.
>
> Changes in v3:
>
> * Changed the place where mutex was locked and unlocked.
>
> drivers/thermal/thermal_core.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
> index 11f0675..8337c27 100644
> --- a/drivers/thermal/thermal_core.c
> +++ b/drivers/thermal/thermal_core.c
> @@ -45,8 +45,10 @@
>
> static DEFINE_MUTEX(thermal_list_lock);
> static DEFINE_MUTEX(thermal_governor_lock);
> +static DEFINE_MUTEX(poweroff_lock);
>
> static atomic_t in_suspend;
> +static bool power_off_triggered;
>
> static struct thermal_governor *def_governor;
>
> @@ -342,7 +344,12 @@ static void handle_critical_trips(struct thermal_zone_device *tz,
> dev_emerg(&tz->device,
> "critical temperature reached(%d C),shutting down\n",
> tz->temperature / 1000);
> - orderly_poweroff(true);
> + mutex_lock(&poweroff_lock);
> + if (!power_off_triggered) {
> + orderly_poweroff(true);
> + power_off_triggered = true;
> + }
> + mutex_unlock(&poweroff_lock);
> }
> }
>
> @@ -1463,6 +1470,7 @@ static int __init thermal_init(void)
> {
> int result;
>
> + mutex_init(&poweroff_lock);
> result = thermal_register_governors();
> if (result)
> goto error;
> @@ -1497,6 +1505,7 @@ static int __init thermal_init(void)
> ida_destroy(&thermal_cdev_ida);
> mutex_destroy(&thermal_list_lock);
> mutex_destroy(&thermal_governor_lock);
> + mutex_destroy(&poweroff_lock);
> return result;
> }
>
>
prev parent reply other threads:[~2017-05-02 3:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 4:29 Keerthy
2017-04-18 4:29 ` [PATCH v6 2/2] thermal: core: Add a back up thermal shutdown mechanism Keerthy
2017-04-18 6:15 ` Ravikumar
2017-04-18 6:18 ` Keerthy
2017-05-02 3:40 ` Keerthy
2017-05-02 3:40 ` Keerthy [this message]
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=5a3df459-0fd7-e042-7e1d-fd76e7652e09@ti.com \
--to=j-keerthy@ti.com \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rui.zhang@intel.com \
--cc=t-kristo@ti.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®