All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Punit Agrawal <punit.agrawal@arm.com>
Cc: linux-pm@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
	Eduardo Valentin <edubezval@gmail.com>,
	linux-kernel@vger.kernel.org, Jean Delvare <jdelvare@suse.de>,
	Peter Feuerer <peter@piie.net>, Heiko Stuebner <heiko@sntech.de>,
	Lukasz Majewski <l.majewski@samsung.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	linux-samsung-soc@vger.kernel.org,
	Guenter Roeck <linux@roeck-us.net>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	Darren Hart <dvhart@infradead.org>,
	lm-sensors@lm-sensors.org
Subject: Re: [PATCH] thermal: consistently use int for temperatures
Date: Tue, 21 Jul 2015 09:31:11 +0200	[thread overview]
Message-ID: <20150721073111.GH5161@pengutronix.de> (raw)
In-Reply-To: <9hhd1zrc9yb.fsf@e105922-lin.cambridge.arm.com>

Hi Punit,

On Fri, Jul 17, 2015 at 12:14:36PM +0100, Punit Agrawal wrote:
> Hi Sascha,
> 
> Sascha Hauer <s.hauer@pengutronix.de> writes:
> 
> > The thermal code uses int, long and unsigned long for temperatures
> > in different places.
> >
> > Using an unsigned type limits the thermal framework to positive
> > temperatures without need. Also several drivers currently will report
> > temperatures near UINT_MAX for temperatures below 0°C. This will probably
> > immediately shut the machine down due to overtemperature if started below
> > 0°C.
> >
> > 'long' is 64bit on several architectures. This is not needed since INT_MAX °mC
> > is above the melting point of all known materials.
> >
> > Consistently use a plain 'int' for temperatures throughout the thermal code and
> > the drivers. This only changes the places in the drivers where the temperature
> > is passed around as pointer, when drivers internally use another type this is
> > not changed.
> >
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> 
> Thanks for moving over the thermal sub-system in Linux to consistently
> use a single type.
> 
> In your patch, you missed migrating over power_allocator governor and
> it's associated trace events. It got merged for v4.2.
> 
> Could you incorporate something like below in your next version?

It seems I have changed drivers/thermal/power_allocator.c but missed
include/trace/events/thermal_power_allocator.h. Please check out the v2
patch I just sent.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

WARNING: multiple messages have this Message-ID (diff)
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] thermal: consistently use int for temperatures
Date: Tue, 21 Jul 2015 09:31:11 +0200	[thread overview]
Message-ID: <20150721073111.GH5161@pengutronix.de> (raw)
In-Reply-To: <9hhd1zrc9yb.fsf@e105922-lin.cambridge.arm.com>

Hi Punit,

On Fri, Jul 17, 2015 at 12:14:36PM +0100, Punit Agrawal wrote:
> Hi Sascha,
> 
> Sascha Hauer <s.hauer@pengutronix.de> writes:
> 
> > The thermal code uses int, long and unsigned long for temperatures
> > in different places.
> >
> > Using an unsigned type limits the thermal framework to positive
> > temperatures without need. Also several drivers currently will report
> > temperatures near UINT_MAX for temperatures below 0?C. This will probably
> > immediately shut the machine down due to overtemperature if started below
> > 0?C.
> >
> > 'long' is 64bit on several architectures. This is not needed since INT_MAX ?mC
> > is above the melting point of all known materials.
> >
> > Consistently use a plain 'int' for temperatures throughout the thermal code and
> > the drivers. This only changes the places in the drivers where the temperature
> > is passed around as pointer, when drivers internally use another type this is
> > not changed.
> >
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> 
> Thanks for moving over the thermal sub-system in Linux to consistently
> use a single type.
> 
> In your patch, you missed migrating over power_allocator governor and
> it's associated trace events. It got merged for v4.2.
> 
> Could you incorporate something like below in your next version?

It seems I have changed drivers/thermal/power_allocator.c but missed
include/trace/events/thermal_power_allocator.h. Please check out the v2
patch I just sent.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

WARNING: multiple messages have this Message-ID (diff)
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Punit Agrawal <punit.agrawal@arm.com>
Cc: linux-pm@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
	Eduardo Valentin <edubezval@gmail.com>,
	linux-kernel@vger.kernel.org, Jean Delvare <jdelvare@suse.de>,
	Peter Feuerer <peter@piie.net>, Heiko Stuebner <heiko@sntech.de>,
	Lukasz Majewski <l.majewski@samsung.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	linux-samsung-soc@vger.kernel.org,
	Guenter Roeck <linux@roeck-us.net>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	Darren Hart <dvhart@infradead.org>,
	lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] [PATCH] thermal: consistently use int for temperatures
Date: Tue, 21 Jul 2015 07:31:11 +0000	[thread overview]
Message-ID: <20150721073111.GH5161@pengutronix.de> (raw)
In-Reply-To: <9hhd1zrc9yb.fsf@e105922-lin.cambridge.arm.com>

Hi Punit,

On Fri, Jul 17, 2015 at 12:14:36PM +0100, Punit Agrawal wrote:
> Hi Sascha,
> 
> Sascha Hauer <s.hauer@pengutronix.de> writes:
> 
> > The thermal code uses int, long and unsigned long for temperatures
> > in different places.
> >
> > Using an unsigned type limits the thermal framework to positive
> > temperatures without need. Also several drivers currently will report
> > temperatures near UINT_MAX for temperatures below 0°C. This will probably
> > immediately shut the machine down due to overtemperature if started below
> > 0°C.
> >
> > 'long' is 64bit on several architectures. This is not needed since INT_MAX °mC
> > is above the melting point of all known materials.
> >
> > Consistently use a plain 'int' for temperatures throughout the thermal code and
> > the drivers. This only changes the places in the drivers where the temperature
> > is passed around as pointer, when drivers internally use another type this is
> > not changed.
> >
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> 
> Thanks for moving over the thermal sub-system in Linux to consistently
> use a single type.
> 
> In your patch, you missed migrating over power_allocator governor and
> it's associated trace events. It got merged for v4.2.
> 
> Could you incorporate something like below in your next version?

It seems I have changed drivers/thermal/power_allocator.c but missed
include/trace/events/thermal_power_allocator.h. Please check out the v2
patch I just sent.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  reply	other threads:[~2015-07-21  7:31 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06  7:19 [PATCH] thermal: consistently use int for temperatures Sascha Hauer
2015-07-06  7:19 ` [lm-sensors] " Sascha Hauer
2015-07-06  7:19 ` Sascha Hauer
2015-07-06  8:34 ` Geert Uytterhoeven
2015-07-06  8:34   ` [lm-sensors] " Geert Uytterhoeven
2015-07-06  8:34   ` Geert Uytterhoeven
2015-07-06  8:34   ` Geert Uytterhoeven
2015-07-06  8:34   ` Geert Uytterhoeven
2015-07-06 10:25 ` Jean Delvare
2015-07-06 10:25   ` [lm-sensors] " Jean Delvare
2015-07-06 10:25   ` Jean Delvare
2015-07-06 10:26 ` Lukasz Majewski
2015-07-06 10:26   ` [lm-sensors] " Lukasz Majewski
2015-07-06 10:26   ` Lukasz Majewski
2015-07-06 10:26   ` Lukasz Majewski
2015-07-06 18:18 ` Darren Hart
2015-07-06 18:18   ` [lm-sensors] " Darren Hart
2015-07-06 18:18   ` Darren Hart
2015-07-06 19:07 ` Heiko Stübner
2015-07-06 19:07   ` [lm-sensors] " Heiko Stübner
2015-07-06 19:07   ` Heiko Stübner
2015-07-06 19:07   ` Heiko Stübner
2015-07-08  8:11 ` Peter Feuerer
2015-07-08  8:11   ` [lm-sensors] " Peter Feuerer
2015-07-08  8:11   ` Peter Feuerer
2015-07-08  8:11   ` Peter Feuerer
2015-07-17 11:14 ` Punit Agrawal
2015-07-17 11:14   ` [lm-sensors] " Punit Agrawal
2015-07-17 11:14   ` Punit Agrawal
2015-07-17 11:14   ` Punit Agrawal
2015-07-21  7:31   ` Sascha Hauer [this message]
2015-07-21  7:31     ` [lm-sensors] " Sascha Hauer
2015-07-21  7:31     ` Sascha Hauer

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=20150721073111.GH5161@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=dvhart@infradead.org \
    --cc=edubezval@gmail.com \
    --cc=heiko@sntech.de \
    --cc=jdelvare@suse.de \
    --cc=l.majewski@samsung.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lm-sensors@lm-sensors.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=peter@piie.net \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=punit.agrawal@arm.com \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@gmail.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 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.