public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>
Subject: Re: coretemp.0 folder contents changed
Date: Mon, 5 May 2014 10:32:31 -0700	[thread overview]
Message-ID: <20140505173231.GA25644@roeck-us.net> (raw)
In-Reply-To: <5367C6A7.5020008@linux.intel.com>

On Mon, May 05, 2014 at 10:13:11AM -0700, Srinivas Pandruvada wrote:
> Hi,
> 
> for kernel : 3.15.rc3 .
> 
> Is there any change in the coretemp? Previously we used to see,
> tempx data (like temp2_input, temp2_max etc.)
> /sys/devices/platform/coretemp.0/.
> 
That isn't where you are supposed to look for hwmon attributes.

> Now We don't see them. Now we have to go
> /sys/devices/platform/coretemp.0/hwmon/hwmon?/ to get these values.
> 
This is also not the correct location.

You should be looking in /sys/class/hwmon/hwmonX/.

There will be a name attribute either in /sys/class/hwmon/hwmonX/name
or in /sys/class/hwmon/hwmonX/device/name. For coretemp, the value
reported in the name attribute will be 'coretemp'. This defines the
directory where the actual sensor attributes will be located.

A better approach might be to use libsensors instead of directly
accessing attributes.

To give you the background, hwmon attributes are in the process of
being moved from the parent device to the hwmon device, or from
/sys/class/hwmon/hwmonX/device/ to /sys/class/hwmon/hwmonX/,
as part of an effort to streamline the code and make it more
consistent and maintainable.

Guenter

  reply	other threads:[~2014-05-05 17:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 17:13 coretemp.0 folder contents changed Srinivas Pandruvada
2014-05-05 17:32 ` Guenter Roeck [this message]
2014-05-05 17:46   ` Srinivas Pandruvada
2014-05-06 11:55   ` [lm-sensors] " Jean Delvare
2014-05-06 13:32     ` Guenter Roeck
2014-05-07  7:13       ` Jean Delvare
2014-05-07 12:10         ` Guenter Roeck
2014-05-09  7:57           ` Jean Delvare
2014-05-06 15:20     ` Srinivas Pandruvada
2014-05-06 15:53       ` Srinivas Pandruvada
2014-05-07  7:16       ` Jean Delvare

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=20140505173231.GA25644@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=fenghua.yu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=srinivas.pandruvada@linux.intel.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