Re: [PATCH] lis3lv02d: provide means to disable polled input interface

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 9 Apr 2010, Éric Piel wrote:

> > This is reported to create 20% CPU usage increase (and proportionaly higher
> > power consumption) just for the ipolldevd kernel thread (which is used
> > to read the sensor).
> > 
> > As most users probably only use the freefall functionality of the driver
> > and not the joystick interface, provide means for disabling the registration
> > of joystick device altogether via module parameter.
> > (I'd rather make it default to 0, but this will break backwards compatibility).
> Are you saying there is a 20% CPU usage even when the joystick interface
> is not open? This should not happen (and this is not happening on my
> laptop). The polling should happen only when a userspace app opens the
> joystick interface (like running neverball).
> 
> So I'd tend to think it's more due to a misconfiguration of the system
> (like xserver using the joystick interface as a pointer device) or it's
> a bug in the way we set up the polling. Could you investigate and let me
> know?

Marcin originally reported this to me.

Marcin, could you please check 'lsof' output to see whether the joystick 
interface has been open by some application?

Thanks,

-- 
Jiri Kosina
SUSE Labs, Novell Inc.

_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors


[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux