On Tue, 2016-04-12 at 17:51 +0530, Rajagopal Aravindan wrote:
On Thu, Mar 31, 2016 at 7:41 PM, Rajagopal Aravindan
<a.rajagopal.81@
gmail.com> wrote:
> On Wed, Mar 16, 2016 at 2:28 AM, Srinivas Pandruvada <srinivas.pand
> ruvada(a)linux.intel.com> wrote:
> > > Srinivas,
> > >
> > > In all the sample XMLs I have come across so far, either sysfs
> > path
> > > or a custom device file path is specified.
> > >
> > > Am I to understand there are also XML tags to specify d-bus
> > object
> > > path and have a method under it invoked ?
> > This is not supported. If you want to add support you can. It
> > will be
> > useful.
> >
> > >
> > > Whether cooling is initiated actively or passively is a cooling
> > > device design choice.
> > >
> > > Why is that information also to be provided for <TripPoint> ?
> > >
> > <Preference>QUIET</Preference>
> > then only passive trip points will be active
> > <Preference>PERFORMANCE</Preference>
> > only active trip points will be active
> >
> > The trip points (temperature where some action will take place)
> > can be
> > different when you want more performance (you may activate a Fan)
> > or
> > when want a quite mode using simply passive cooling.
> >
> >
> > > Also, it appears that trip point violation doesn't always lead
> > to
> > > cooling, some times it activates frequent temp sensing.
> > Internally based on the you active/passive trip point internally
> > we set
> > another trip point to activate polling. Sometimes when system is
> > busy,
> > you will miss the uevents when you are running thermald without
> > polling
> > for temperature. If your are polling for temperature change or
> > you have
> > sensors which can't notify temperature change asynchronously then
> > this
> > trip is not much value.
> >
> > You can read ACPI 6.0 spec thermal handling chapter. The trip and
> > zones
> > are modeled as defined here.
> >
> > Thanks,
> > Srinivas
> >
> > > This was my run-time observation on my target h/w.
> > > It would be very helpful if you could point to some links /
> > documents
> > > or provide more details on trip points.
> > >
> > > Thanks & Regards,
> > > Rajagopal
> >
> Srinivas,
>
Hi,
> Could you please provide your inputs on the below ?
> max - I couldn't get info on this trip point type from ACPI 6.0
> spec.
This is not defined in ACPI spec.
> Is there any limit on the max no of trip points for an async-
> capable sensor ?
No. The lowest trip will trigger polling.
> Is there anything like a pure async mode ?
No. As the
uevents reliability reduces depending on other load in the
system. So we will start polling.
> How to go about adding D-Bus support, for both sensing &
throttling
> ?
We have dbus Interface to control many thd_dbus_interface.xml.
These are request to thermald not from thermald. We don't have a way
send a dbus message from thermald to other process for throttling.
So you have to implement.
> Are there XML tags already available, for which parsing &
> operational logic needs to be implemented ?
> If we were to define new tags, will it have to conform to or comply
> with any spec ?
There is no spec.
> Are there devices already available in market, which expose
sensing
> & throttling interfaces via D-Bus ?
I am not aware of any.
Thanks,
Srinivas
>
> Thanks & Regards,
> Rajagopal
>
Srinivas,
Awaiting your inputs on this.
Thanks & Regards,
Rajagopal