All of lore.kernel.org
 help / color / mirror / Atom feed
From: <samu.p.onkalo@nokia.com>
To: <marcin@derlukiewicz.pl>, <jkosina@suse.cz>,
	<eric.piel@tremplin-utc.net>
Cc: <akpm@linux-foundation.org>, <pavel@ucw.cz>,
	<lm-sensors@lm-sensors.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] lis3lv02d: provide means to disable polled input interface
Date: Fri, 16 Apr 2010 14:00:15 +0200	[thread overview]
Message-ID: <62697B07E9803846BC582181BD6FB6B826A8525E8A@NOK-EUMSG-02.mgdnok.nokia.com> (raw)
In-Reply-To: <op.va86rulwgp7y00@linux-r26l.site>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2200 bytes --]



>-----Original Message-----
>From: ext Marcin Derlukiewicz [mailto:marcin@derlukiewicz.pl]
>Sent: 16 April, 2010 14:42
>To: Jiri Kosina; Éric Piel
>Cc: Andrew Morton; Onkalo Samu.P (Nokia-D/Tampere); Pavel Machek; lm-
>sensors@lm-sensors.org; linux-kernel@vger.kernel.org
>Subject: Re: [PATCH] lis3lv02d: provide means to disable polled input
>interface
>
>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
>

Could you check what is the polling period of the device.
something like:
cat /sys/devices/platform/lis3lv02d/input/input9/poll

it is current polling period in milliseconds. 0 disables polling.

-Samu

ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

WARNING: multiple messages have this Message-ID (diff)
From: <samu.p.onkalo@nokia.com>
To: marcin@derlukiewicz.pl, jkosina@suse.cz, eric.piel@tremplin-utc.net
Cc: akpm@linux-foundation.org, pavel@ucw.cz,
	lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] lis3lv02d: provide means to disable polled
Date: Fri, 16 Apr 2010 12:00:15 +0000	[thread overview]
Message-ID: <62697B07E9803846BC582181BD6FB6B826A8525E8A@NOK-EUMSG-02.mgdnok.nokia.com> (raw)
In-Reply-To: <op.va86rulwgp7y00@linux-r26l.site>



>-----Original Message-----
>From: ext Marcin Derlukiewicz [mailto:marcin@derlukiewicz.pl]
>Sent: 16 April, 2010 14:42
>To: Jiri Kosina; Éric Piel
>Cc: Andrew Morton; Onkalo Samu.P (Nokia-D/Tampere); Pavel Machek; lm-
>sensors@lm-sensors.org; linux-kernel@vger.kernel.org
>Subject: Re: [PATCH] lis3lv02d: provide means to disable polled input
>interface
>
>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?id54953
>

Could you check what is the polling period of the device.
something like:
cat /sys/devices/platform/lis3lv02d/input/input9/poll

it is current polling period in milliseconds. 0 disables polling.

-Samu

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

  reply	other threads:[~2010-04-16 12:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 12:56 [PATCH] lis3lv02d: provide means to disable polled input interface Jiri Kosina
2010-04-09 12:56 ` [lm-sensors] [PATCH] lis3lv02d: provide means to disable polled Jiri Kosina
2010-04-09 13:29 ` [PATCH] lis3lv02d: provide means to disable polled input interface Éric Piel
2010-04-09 13:29   ` [lm-sensors] [PATCH] lis3lv02d: provide means to disable polled Éric Piel
2010-04-09 13:32   ` [PATCH] lis3lv02d: provide means to disable polled input interface Jiri Kosina
2010-04-09 13:32     ` [lm-sensors] [PATCH] lis3lv02d: provide means to disable polled Jiri Kosina
2010-04-09 18:11     ` [lm-sensors] [PATCH] lis3lv02d: provide means to disable polled input interface Jean Delvare
2010-04-09 18:11       ` [lm-sensors] [PATCH] lis3lv02d: provide means to disable polled Jean Delvare
2010-04-16 11:41     ` [PATCH] lis3lv02d: provide means to disable polled input interface Marcin Derlukiewicz
2010-04-16 11:41       ` [lm-sensors] [PATCH] lis3lv02d: provide means to disable polled Marcin Derlukiewicz
2010-04-16 12:00       ` samu.p.onkalo [this message]
2010-04-16 12:00         ` samu.p.onkalo
2010-04-16 12:13         ` [PATCH] lis3lv02d: provide means to disable polled input interface Marcin Derlukiewicz
2010-04-16 12:13           ` [lm-sensors] [PATCH] lis3lv02d: provide means to disable polled Marcin Derlukiewicz
2010-04-16 13:56           ` [PATCH] lis3lv02d: provide means to disable polled input interface Éric Piel
2010-04-16 13:56             ` [lm-sensors] [PATCH] lis3lv02d: provide means to disable polled Éric Piel
2010-04-16 14:26             ` [PATCH] lis3lv02d: provide means to disable polled input interface Marcin Derlukiewicz
2010-04-16 14:26               ` [lm-sensors] [PATCH] lis3lv02d: provide means to disable polled Marcin Derlukiewicz
2010-04-16 14:30               ` [PATCH] lis3lv02d: provide means to disable polled input interface Éric Piel
2010-04-16 14:30                 ` [lm-sensors] [PATCH] lis3lv02d: provide means to disable polled Éric Piel
2010-04-16 12:06       ` [PATCH] lis3lv02d: provide means to disable polled input interface Éric Piel
2010-04-16 12:06         ` [lm-sensors] [PATCH] lis3lv02d: provide means to disable polled Éric Piel
2010-04-09 21:41   ` [PATCH] lis3lv02d: provide means to disable polled input interface Frans Pop

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=62697B07E9803846BC582181BD6FB6B826A8525E8A@NOK-EUMSG-02.mgdnok.nokia.com \
    --to=samu.p.onkalo@nokia.com \
    --cc=akpm@linux-foundation.org \
    --cc=eric.piel@tremplin-utc.net \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=marcin@derlukiewicz.pl \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.