From: Eduardo Valentin <edubezval@gmail.com>
To: Keerthy <j-keerthy@ti.com>
Cc: rui.zhang@intel.com, 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 v4 1/2] thermal: core: Allow orderly_poweroff to be called only once
Date: Fri, 14 Apr 2017 08:40:10 -0700 [thread overview]
Message-ID: <20170414154008.GC24429@localhost.localdomain> (raw)
In-Reply-To: <1492159933-4213-1-git-send-email-j-keerthy@ti.com>
[-- Attachment #1: Type: text/plain, Size: 2815 bytes --]
On Fri, Apr 14, 2017 at 02:22:12PM +0530, 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.
>
> Reported-by: Keerthy <j-keerthy@ti.com>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
Not sure I have seen the above tagging before.
Anyways, Rui, please pick this one, or let me know if you prefer me to
queue it for you.
Acked-by: Eduardo Valentin <edubezval@gmail.com>
> ---
>
> Changes in v4:
>
> * power_off_triggered declaration together with mutex definition.
>
> Changes in v3:
>
> * Changed the place where mutex was locked and unlocked.
>
> Changes in v2:
>
> * Added a global mutex to serialize poweroff code sequence.
>
> 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;
> }
>
> --
> 1.9.1
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-04-14 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 8:52 [PATCH v4 1/2] thermal: core: Allow orderly_poweroff to be called only once Keerthy
2017-04-14 8:52 ` [PATCH v4 2/2] thermal: core: Add a back up thermal shutdown mechanism Keerthy
2017-04-14 15:38 ` Eduardo Valentin
2017-04-14 15:42 ` Eduardo Valentin
2017-04-14 18:18 ` Eduardo Valentin
2017-04-15 3:16 ` Keerthy
2017-04-14 15:40 ` Eduardo Valentin [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=20170414154008.GC24429@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=j-keerthy@ti.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;
as well as URLs for NNTP newsgroup(s).