public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH/RFC: driver model/pmcore wakeup hooks (1/4)
Date: Tue, 5 Oct 2004 14:53:27 -0700	[thread overview]
Message-ID: <200410051453.27629.david-b@pacbell.net> (raw)
In-Reply-To: <20041005201531.GA5763@elf.ucw.cz>

On Tuesday 05 October 2004 1:15 pm, Pavel Machek wrote:

> > Also, so strncmp() can be used.  It won't matter if the sysadmin goes
> > 
> >    echo -n enabled > wakeup
> >    echo enabled > wakeup
> 
> Well, you could make that 0,1. That would be more sysfs-style...

Only for things like detach_state and power_state, which shouldn't
be numbers in the first place ... :)

The /sys/module/*/OPTION strings use Y/N for booleans, and
maybe sysfs should actually have generic code to read/write
such boolean values.


> On the second thought, perhaps file simply should not be there if
> wakeup is not supported.

That doesn't work too well for things like USB, where one config
may support wakeup but another doesn't ... and unconfigured
devices never support it.  The "can_support" value changes
over time.

- Dave

  reply	other threads:[~2004-10-05 21:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 21:00 PATCH/RFC: driver model/pmcore wakeup hooks (1/4) David Brownell
2004-10-05 19:37 ` Pavel Machek
2004-10-05 20:09   ` David Brownell
2004-10-05 20:15     ` Pavel Machek
2004-10-05 21:53       ` David Brownell [this message]
2004-10-16  6:03     ` Len Brown
2004-10-19  3:41       ` David Brownell
2004-10-19  4:55         ` [ACPI] " Hiroshi 2 Itoh
2004-10-19  5:18           ` David Brownell
2004-10-20  6:16         ` Len Brown
  -- strict thread matches above, loose matches on Subject: below --
2004-10-19  9:11 Li, Shaohua

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=200410051453.27629.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --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