[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4D68720C2E767A4AA6A8796D42C8EB5904C758@BGSMSX101.gar.corp.intel.com>
Date: Tue, 13 Mar 2012 04:48:23 +0000
From: "R, Durgadoss" <durgadoss.r@...el.com>
To: Amit Kachhap <amit.kachhap@...aro.org>
CC: "linux-pm@...ts.linux-foundation.org"
<linux-pm@...ts.linux-foundation.org>,
"linux-samsung-soc@...r.kernel.org"
<linux-samsung-soc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mjg59@...f.ucam.org" <mjg59@...f.ucam.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"lenb@...nel.org" <lenb@...nel.org>,
"linaro-dev@...ts.linaro.org" <linaro-dev@...ts.linaro.org>,
"lm-sensors@...sensors.org" <lm-sensors@...sensors.org>,
"eduardo.valentin@...com" <eduardo.valentin@...com>,
"patches@...aro.org" <patches@...aro.org>
Subject: RE: [PATCH 1/4] thermal: exynos: Add thermal interface support for
linux thermal layer
Hi Amit,
[snip.]
> >> +
> >> + kobject_uevent(&th_zone->therm_dev->device.kobj, KOBJ_CHANGE);
> >
> > Wouldn't it make more sense to pass the trip point id also as an 'env'
> > parameter ? This way, the user space can easily figure out which trip
> > point has been crossed.
> Its a good suggestion. I will check if some uevent property allows that.
The kobject_uevent_env(...) call allows that. The third argument takes a
char *envp[]. For example, We could pass "trip=0" to indicate the trip point.
I should have mentioned this in my previous reply itself..missed it..
Thanks,
Durga
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists