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? Is it ok if we add this in a separate series ? -- <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook | <http://twitter.com/#!/linaroorg> Twitter | <http://www.linaro.org/linaro-blog/> Blog
