public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "Éric Piel" <eric.piel@tremplin-utc.net>,
	"Marcin Derlukiewicz" <marcin@derlukiewicz.pl>,
	linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org,
	"Pavel Machek" <pavel@ucw.cz>,
	"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [lm-sensors] [PATCH] lis3lv02d: provide means to disable polled input interface
Date: Fri, 9 Apr 2010 20:11:10 +0200	[thread overview]
Message-ID: <20100409201110.5d75a24e@hyperion.delvare> (raw)
In-Reply-To: <alpine.LNX.2.00.1004091532150.8345@pobox.suse.cz>

On Fri, 9 Apr 2010 15:32:59 +0200 (CEST), Jiri Kosina wrote:
> 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?

I would randomly blame hal. It keeps my IR remote control device opened
all the time and I have no idea why.

-- 
Jean Delvare

  reply	other threads:[~2010-04-09 18:11 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
2010-04-09 13:32   ` Jiri Kosina
2010-04-09 18:11     ` Jean Delvare [this message]
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=20100409201110.5d75a24e@hyperion.delvare \
    --to=khali@linux-fr.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox