public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Éric Piel" <eric.piel@tremplin-utc.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Samu Onkalo <samu.p.onkalo@nokia.com>,
	Pavel Machek <pavel@ucw.cz>,
	lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org,
	Marcin Derlukiewicz <marcin@derlukiewicz.pl>
Subject: Re: [PATCH] lis3lv02d: provide means to disable polled input interface
Date: Fri, 09 Apr 2010 15:29:53 +0200	[thread overview]
Message-ID: <4BBF2BD1.5050107@tremplin-utc.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1004091453530.8345@pobox.suse.cz>

On 09/04/10 14:56, Jiri Kosina wrote:
> lis3lv02d driver creates emulated joystick interface for events reported 
> by the sensor.
> Because of HW, this has to be implemented as polled input device, with
> 20Hz frequency.
> 
> 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?

Cheers,
Eric

  reply	other threads:[~2010-04-09 13:29 UTC|newest]

Thread overview: 12+ 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 13:29 ` Éric Piel [this message]
2010-04-09 13:32   ` Jiri Kosina
2010-04-09 18:11     ` [lm-sensors] " Jean Delvare
2010-04-16 11:41     ` Marcin Derlukiewicz
2010-04-16 12:00       ` samu.p.onkalo
2010-04-16 12:13         ` Marcin Derlukiewicz
2010-04-16 13:56           ` Éric Piel
2010-04-16 14:26             ` Marcin Derlukiewicz
2010-04-16 14:30               ` Éric Piel
2010-04-16 12:06       ` Éric Piel
2010-04-09 21:41   ` 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=4BBF2BD1.5050107@tremplin-utc.net \
    --to=eric.piel@tremplin-utc.net \
    --cc=akpm@linux-foundation.org \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=marcin@derlukiewicz.pl \
    --cc=pavel@ucw.cz \
    --cc=samu.p.onkalo@nokia.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox