All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@linux.intel.com>
To: samu.p.onkalo@nokia.com
Cc: gregkh@suse.de, Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: sysfs and power management
Date: Wed, 27 Oct 2010 12:48:16 +0100	[thread overview]
Message-ID: <20101027124816.7087436a@linux.intel.com> (raw)
In-Reply-To: <1288177143.12206.22.camel@4fid08082>

> I started to wonder if it makes sense to enhance sysfs so that it
> optionally prodives open / close call backs. Internally sysfs has
> some bookkeeping about the refcount but this is not visible to the
> driver. Of course majority of the sysfs users doesn't need that at all
> and for them this is just overhead. 

I think we need it. There doesn't need to be much overhead however as
there is no need (or sense) in providing per sysfs node open/close
hooks.

The pm layer also lacks a clean race-free way to actually ascertain
when the device was last kicked out of pm saving.

  reply	other threads:[~2010-10-27 12:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 10:59 sysfs and power management Onkalo Samu
2010-10-27 11:48 ` Alan Cox [this message]
2010-10-27 13:43   ` samu.p.onkalo
2010-10-27 14:28     ` Alan Cox
2010-10-29 19:50       ` Greg KH
2010-10-30 14:00         ` Henrique de Moraes Holschuh
2010-10-31 11:57           ` Onkalo Samu
2010-10-31 14:25             ` Greg KH
2010-11-01 10:41               ` Onkalo Samu
2010-11-01 16:57                 ` Alan Cox
2010-11-01 18:07                   ` Greg KH
2010-11-03  9:44                     ` Alan Cox
2010-11-03 10:48                       ` samu.p.onkalo
2010-11-03 13:09                       ` Greg KH
2010-11-03 15:00                         ` samu.p.onkalo

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=20101027124816.7087436a@linux.intel.com \
    --to=alan@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.