From: Brian Norris <computersforpeace@gmail.com>
To: linux-pm@vger.kernel.org
Cc: "R.Durgadoss" <durgadoss.r@intel.com>,
Len Brown <len.brown@intel.com>,
Lukasz Majewski <l.majewski@samsung.com>,
Eduardo Valentin <edubezval@gmail.com>
Subject: Re: thermal: uevent/netlink with step_wise?
Date: Wed, 1 Apr 2015 14:17:18 -0700 [thread overview]
Message-ID: <20150401211718.GA32500@ld-irv-0074> (raw)
In-Reply-To: <20150331224348.GZ32500@ld-irv-0074>
On Tue, Mar 31, 2015 at 03:43:48PM -0700, Brian Norris wrote:
> Particularly, I'm looking right now at using the uevent/netlink
> notification mechanism. It seems that this is only active when we use
> the 'user_space' governor, meaning I can't get any user-space
> notifications when using the in-kernel governor. Am I missing something,
> or is this a known limitation? Is there any reason we can't enable both?
> For the user-space side, I'd mostly be interested in being a consumer;
> e.g., display warnings in high-temperature scenarios; although I might
> also use it to trigger some user-space cooling mechanisms.
I'm noticing two additional interesting details.
1. There's a separate netlink event mechanism that has never been used.
See generate_netlink_event(), from this commit:
commit 4cb18728709683c91a5f6f8d5f337bfb498b089a
Author: R.Durgadoss <durgadoss.r@intel.com>
Date: Wed Oct 27 03:33:29 2010 +0530
thermal: Add event notification to thermal framework
2. The Samsung Exynos thermal driver reports uevent info directly, no
matter which governor is in use. See exynos_report_trigger(). Is it
acceptable to augment drivers in this way, or wouldn't it make more
sense to improve the core framework to support this type of
notification?
Brian
next prev parent reply other threads:[~2015-04-01 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 22:43 thermal: uevent/netlink with step_wise? Brian Norris
2015-04-01 21:17 ` Brian Norris [this message]
2015-04-02 4:28 ` R, Durgadoss
2015-04-02 5:11 ` Brian Norris
2015-04-02 5:28 ` R, Durgadoss
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=20150401211718.GA32500@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=durgadoss.r@intel.com \
--cc=edubezval@gmail.com \
--cc=l.majewski@samsung.com \
--cc=len.brown@intel.com \
--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