public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Keerthy <j-keerthy@ti.com>
To: linux-kernel@vger.kernel.org, oleg@redhat.com, toshi.kani@hp.com,
	linux-omap@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-patch-review@list.ti.com
Cc: j-keerthy@ti.com, nm@ti.com, grygorii.strashko@ti.com,
	mingo@kernel.org, josh@joshtriplett.org, rui.zhang@intel.com,
	edubezval@gmail.com
Subject: [PATCH 2/2] thermal: Use emergency_poweroff instead of orderly_poweroff for shutdown scenario
Date: Thu, 28 Jan 2016 18:36:29 +0530	[thread overview]
Message-ID: <1453986389-15887-3-git-send-email-j-keerthy@ti.com> (raw)
In-Reply-To: <1453986389-15887-1-git-send-email-j-keerthy@ti.com>

Currently when the system reaches dangerously high temperatures we are
calling orderly_poweroff function to gracefully shutdown the user space
and then power off the system. In the probe phase the orderly_poweroff
might fail leaving the system running at dangerously high temperatures.
Hence calling the emergency_poweroff function which shuts down the
system after a configurable period of time.

Signed-off-by: Keerthy <j-keerthy@ti.com>
---
 drivers/thermal/thermal_core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
index a0a8fd1..220fc94 100644
--- a/drivers/thermal/thermal_core.c
+++ b/drivers/thermal/thermal_core.c
@@ -446,7 +446,7 @@ 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);
+		emergency_poweroff();
 	}
 }
 
-- 
1.9.1


  parent reply	other threads:[~2016-01-28 13:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 13:06 [PATCH 0/2] reboot: Introduce emergency_poweroff function Keerthy
2016-01-28 13:06 ` [PATCH 1/2] reboot: Introduce emergency poweroff function Keerthy
2016-01-28 13:06 ` Keerthy [this message]
2016-01-28 13:24 ` [PATCH 0/2] reboot: Introduce emergency_poweroff function One Thousand Gnomes
2016-01-29  1:45   ` Keerthy

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=1453986389-15887-3-git-send-email-j-keerthy@ti.com \
    --to=j-keerthy@ti.com \
    --cc=edubezval@gmail.com \
    --cc=grygorii.strashko@ti.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-patch-review@list.ti.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=nm@ti.com \
    --cc=oleg@redhat.com \
    --cc=rui.zhang@intel.com \
    --cc=toshi.kani@hp.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