lkml.org 
[lkml]   [2010]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] lis3lv02d: provide means to disable polled input interface
Date
From
Dnia 09-04-2010 o 15:32:59 Jiri Kosina <jkosina@suse.cz> napisał(a):

> 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,
>

sorry for the delay, had a crunch time

here is the link for this lsof:
https://bugzilla.novell.com/attachment.cgi?id=354953


Best regards,
Marcin.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2010-04-16 13:45    [W:0.080 / U:0.092 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site