Re: [ANNOUNCE] System Inactivity Monitor v1.0

[Vojtech Pavlik <vojtech@suse.cz>]

On Tue, Jan 30, 2007 at 01:33:10PM +0100, Alessandro Di Marco wrote:
> Vojtech Pavlik <vojtech@suse.cz> writes:
> 
>    On Mon, Jan 29, 2007 at 11:42:08PM +0100, Alessandro Di Marco wrote:
> 
>    > OK, but what about the time-warp problem?. To fix it I need to know when the
>    > system goes to sleep/resumes. In SIN I've solved via the platform driver,
>    > introducing suspend() resume() callbacks...
> 
>    Well, you just need to make sure that a resume() actually is a visible
>    event ...
> 
> Sorry, but I don't see the point. Visible to what? 

Counted as activity.

> Mine problem here is that the input device doesn't care about suspend/resume
> cycles (it is a straight char driver), probably because it doesn't need to (so
> far.) Low-level drivers (kbd & co) on the contrary are all bus or platform
> drivers, hooking directly into suspend/resume callbacks.
> 
> Do you mean that I should back-propagate a suspend/resume event from the
> low-level drivers to the input one?
 
Yes, but not as a callback, but instead as an input event. 

-- 
Vojtech Pavlik
Director SuSE Labs