mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: "Zhang, Rui" <rui.zhang@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"srikars@nvidia.com" <srikars@nvidia.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"mlongnecker@nvidia.com" <mlongnecker@nvidia.com>
Subject: Re: [PATCH v2] thermal: add sysfs_notify on some attributes
Date: Wed, 30 Mar 2016 10:06:31 -0700	[thread overview]
Message-ID: <1459357591.13525.62.camel@linux.intel.com> (raw)
In-Reply-To: <20160329013540.GA15615@localhost.localdomain>

On Mon, 2016-03-28 at 18:35 -0700, Eduardo Valentin wrote:
> On Tue, Mar 15, 2016 at 11:08:00PM +0000, Pandruvada, Srinivas wrote:
> > 
> > On Mon, 2016-03-14 at 11:12 -0700, Srikar Srimath Tirumala wrote:
> > > 
> > > 
[...]
> > 
> The complexity of such communication (or even the current status of
> sysfs ABI) starts to reach limit of such channel. We may definitely
> consider other means, such as /dev interface, just like IIO does.
Yes. Instead of loading netlink I/F, we need to have thermal channel to
notify.

> > During last LPC we discussed about using IIO for temperature
> > threshold
> > notifications and I submitted multiple changes for that. Looks like
> > we
> > also care of trip point changes. So I think we need more
> > comprehensive
> > mechanism to address this.
> > 
> > May be we should have thermal mini summit during LPC again and
> > decide a
> > comprehensive plan to address all asynchronous thermal
> > notifications.
> > 
> I have created a wiki for LPC 2016
> http://wiki.linuxplumbersconf.org/2016:thermal
> 
> Overall I believe we need to solve the (temperature) sensing in a
> more
> structured way within the kernel. We have three subsystem that allow
> performing temperature sensing. They are different in design and
> concept, but still solve similar problems.
> 
> Again, please lets generate enough quorum to run the micro conf.
> 
I am planning to attend.

Thanks,
Srinivas
> BR, 
> 
> Eduardo Valentin

      parent reply	other threads:[~2016-03-30 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 18:12 Srikar Srimath Tirumala
2016-03-15 23:08 ` Pandruvada, Srinivas
2016-03-29  1:35   ` Eduardo Valentin
2016-03-30  2:53     ` Srikar Srimath Tirumala
2016-03-30 15:45       ` Pandruvada, Srinivas
2016-03-30 17:06     ` Srinivas Pandruvada [this message]

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=1459357591.13525.62.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=edubezval@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mlongnecker@nvidia.com \
    --cc=rui.zhang@intel.com \
    --cc=srikars@nvidia.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

Powered by JetHome