ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Eduardo Valentin <edubezval@gmail.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: Zhang Rui <rui.zhang@intel.com>, Jean Delvare <jdelvare@suse.com>
Subject: [Ksummit-discuss] [TECH TOPIC] [CORE TOPIC] The three ways of temperature sensing in Linux
Date: Mon, 24 Aug 2015 23:12:10 -0700	[thread overview]
Message-ID: <20150825061208.GA13186@localhost.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]

Hi all,

[Not sure if this is TECH or CORE, as it touches more than one
subsystem]

Not sure how late it is to post this, but I am trying anyway.

During LPC 2015 last week it came out the topic of the interaction
between the thermal subsystem with HWMON. On top of it, we also got a
proposal [1] of having thermal exposing its registered devices as IIO.

I know the three subsystem coexist today for some years. They also have
their own design goals. However, the fact that we have three different
subsystems for doing very similar task may be confusing, for the driver
writer, and for user space too.

Another aspect of it is the possible code duplication. For example, it
would interesting to get board temperature sensors, typically registered
as hwmon devices, to be available in the thermal subsystem while
constructing thermal zones out of them. Some user process would expect
the opposite though, to read the thermal zone sensors as hwmon devices,
or as IIO devices.

Therefore, it would be interesting to have a better convergence on how
these subsystems talk to each other, and how this is exposed to user
space. 

The involved maintainers are:
HWMON:
M:      Jean Delvare <jdelvare@suse.com>
M:      Guenter Roeck <linux@roeck-us.net>

Thermal:
M:      Zhang Rui <rui.zhang@intel.com>
M:      Eduardo Valentin <edubezval@gmail.com>

IIO:
M:      Jonathan Cameron <jic23@kernel.org>

BR,

Eduardo Valentin

[1] - http://comments.gmane.org/gmane.linux.kernel.iio/19627


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

             reply	other threads:[~2015-08-25  6:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25  6:12 Eduardo Valentin [this message]
2015-08-25  6:26 ` Krzysztof Kozlowski
2015-08-25 14:03   ` Guenter Roeck
2015-08-25 21:26     ` Eduardo Valentin
2015-08-25 21:13   ` Eduardo Valentin
2015-08-25 21:31 ` Heiko Stuebner
2015-08-25 23:55   ` Guenter Roeck
2015-08-26  0:12     ` Eduardo Valentin
2015-08-26  4:14       ` Guenter Roeck
2015-08-26  6:04       ` Jonathan Cameron

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=20150825061208.GA13186@localhost.localdomain \
    --to=edubezval@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=rui.zhang@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