On Wed, 2020-07-01 at 18:31 +0200, Daniel Lezcano wrote: > On 01/07/2020 17:49, Srinivas Pandruvada wrote: > > [...] > > > > > Then I'd prefer we only introduce the events that are used or > > > will be > > > used soon, like the tz disable/enable, to avoid some potential > > > dead > > > code. > > > We can easily add more events when they are needed. > > > > > > Srinivas, do you have plan to use the trip add/delete events? > > Yes and also trip modify. > > Ok I will keep those then. > > > Also I need to have one more event for heartbeat like event which > > needs > > confirmation from user space to hardware the user process > > controlling > > thermal is active not dead. So whenever hardware wants to check > > health > > it will send an event, which user space should acknowledge > > Could it be the opposite? The userspace sends periodically a message > to > tell it is alive instead of having the kernel asking the userspace? > Kernel doesn't ask (there is no timer in the kernel). The HW/FW send special event for confirmation and expects reply (This is upto the vendors). So user space can't send randomly.
> Is it ok if we add this in a separate series ? Yes. Thanks, Srinivas > > >
