linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Valentin <eduardo.valentin@ti.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, linux-pm@vger.kernel.org,
	linux-omap@vger.kernel.org,
	Eduardo Valentin <eduardo.valentin@ti.com>
Subject: [PATCH 04/14] staging: ti-soc-thermal: report alert events on OMAP4 devices
Date: Mon, 1 Apr 2013 12:04:36 -0400	[thread overview]
Message-ID: <1364832286-17304-5-git-send-email-eduardo.valentin@ti.com> (raw)
In-Reply-To: <1364832286-17304-1-git-send-email-eduardo.valentin@ti.com>

OMAP4460 and OMAP4470 devices have the capability to generate
alert temperature. Thus, whenever a T_ALERT IRQ is served,
the ti-bandgap will call .report_temperature to notify the
thermal framework about thermal zone update request.

This patch allows OMAP4460 and OMAP4470 devices to notify
the thermal framework about T_ALERT events.

Signed-off-by: Eduardo Valentin <eduardo.valentin@ti.com>
---
 .../staging/ti-soc-thermal/omap4-thermal-data.c    |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/drivers/staging/ti-soc-thermal/omap4-thermal-data.c b/drivers/staging/ti-soc-thermal/omap4-thermal-data.c
index 49d0324..ee9c902 100644
--- a/drivers/staging/ti-soc-thermal/omap4-thermal-data.c
+++ b/drivers/staging/ti-soc-thermal/omap4-thermal-data.c
@@ -216,6 +216,7 @@ const struct ti_bandgap_data omap4460_data = {
 	.adc_end_val = OMAP4460_ADC_END_VALUE,
 	.expose_sensor = ti_thermal_expose_sensor,
 	.remove_sensor = ti_thermal_remove_sensor,
+	.report_temperature = ti_thermal_report_sensor_temperature,
 	.sensors = {
 		{
 		.registers = &omap4460_mpu_temp_sensor_registers,
@@ -248,6 +249,7 @@ const struct ti_bandgap_data omap4470_data = {
 	.adc_end_val = OMAP4460_ADC_END_VALUE,
 	.expose_sensor = ti_thermal_expose_sensor,
 	.remove_sensor = ti_thermal_remove_sensor,
+	.report_temperature = ti_thermal_report_sensor_temperature,
 	.sensors = {
 		{
 		.registers = &omap4460_mpu_temp_sensor_registers,
-- 
1.7.7.1.488.ge8e1c


  parent reply	other threads:[~2013-04-01 16:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01 16:04 [PATCH 00/14] staging: ti-soc-thermal: fixes and trending support Eduardo Valentin
2013-04-01 16:04 ` [PATCH 01/14] staging: ti-soc-thermal: return error in case power switch is not supported Eduardo Valentin
2013-04-01 16:04 ` [PATCH 02/14] staging: ti-soc-thermal: remove kernel-doc warnings reported with -v Eduardo Valentin
2013-04-01 16:04 ` [PATCH 03/14] staging: ti-soc-thermal: expose ti_thermal_report_temperature Eduardo Valentin
2013-04-01 16:04 ` Eduardo Valentin [this message]
2013-04-01 16:04 ` [PATCH 05/14] staging: ti-soc-thermal: report alert events on OMAP5 devices Eduardo Valentin
2013-04-01 16:04 ` [PATCH 06/14] staging: ti-soc-thermal: Add counter_delay_mask field to temp_sensor_registers struct Eduardo Valentin
2013-04-01 16:04 ` [PATCH 07/14] staging: ti-soc-thermal: Initialise counter_delay field for OMAP5 sensors Eduardo Valentin
2013-04-01 16:04 ` [PATCH 08/14] staging: ti-soc-thermal: Introduce HAS_COUNTER_DELAY feature for bandgap Eduardo Valentin
2013-04-01 16:04 ` [PATCH 09/14] staging: ti-soc-thermal: Enable COUNTER_DELAY feature for OMAP5 Eduardo Valentin
2013-04-01 16:04 ` [PATCH 10/14] staging: ti-soc-thermal: Modify update_interval r/w functions to incorporate the OMAP5 feature of COUNTER_DELAY Eduardo Valentin
2013-04-01 16:04 ` [PATCH 11/14] staging: ti-soc-thermal: Introduce HAS_HISTORY_BUFFER feature for bandgap Eduardo Valentin
2013-04-01 16:04 ` [PATCH 12/14] staging: ti-soc-thermal: Enable HISTORY_BUFFER Feature for OMAP5 Eduardo Valentin
2013-04-01 16:04 ` [PATCH 13/14] staging: ti-soc-thermal:Introduce ti_bandgap_get_trend function " Eduardo Valentin
2013-04-01 16:04 ` [PATCH 14/14] staging: ti-soc-thermal: Add get_trend support Eduardo Valentin

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=1364832286-17304-5-git-send-email-eduardo.valentin@ti.com \
    --to=eduardo.valentin@ti.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    /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).