All of lore.kernel.org
 help / color / mirror / Atom feed
From: Todd Poynor <tpoynor@mvista.com>
To: Andrew Zabolotny <zap@homelink.ru>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: two patches - request for comments
Date: Fri, 28 May 2004 14:59:53 -0700	[thread overview]
Message-ID: <40B7B659.9010507@mvista.com> (raw)
In-Reply-To: <20040529012030.795ad27e.zap@homelink.ru>

Hi, you're adding new interfaces for power management of LCD and 
backlight devices.  Since there's already LDM/sysfs interfaces for 
reading and writing power state of generic devices, is it necessary to 
add ones particular to these devices or device classes?  In other words, 
is /sys/devices/<bus>/<device>/power/state not suitable for these purposes?

And if a PM interface for device classes is needed that ties into the 
device driver suspend/resume callbacks, perhaps it can be modeled more 
closely on the existing interfaces?  These new interfaces seem to be 
intended to define: 0 == power off, 1 ==  power on.  The existing 
ACPI-inspired interfaces use: 0 == power on/full-power, 1/2/3/4 == 
low-power/off state.

New files don't have GPL license comments.

-- 
Todd

  reply	other threads:[~2004-05-28 22:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 21:20 two patches - request for comments Andrew Zabolotny
2004-05-28 21:59 ` Todd Poynor [this message]
2004-05-29  8:10   ` Andrew Zabolotny
2004-06-01 20:09     ` Todd Poynor
2004-06-01 21:00       ` Andrew Zabolotny
2004-06-02 17:15         ` Greg KH
2004-06-02 21:25           ` Andrew Zabolotny
2004-06-02 21:32           ` Russell King
2004-06-04 20:43             ` Greg KH
2004-05-28 22:10 ` Greg KH
2004-05-29  8:44   ` Andrew Zabolotny
2004-06-01 21:23     ` Jeff Garzik
2004-06-01 21:57       ` Andrew Zabolotny
2004-06-02 17:12         ` Greg KH
2004-05-29 13:46 ` Denis Vlasenko

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=40B7B659.9010507@mvista.com \
    --to=tpoynor@mvista.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zap@homelink.ru \
    /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.