mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Shawn Starr <shawn.starr@rogers.com>
Cc: acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ACPI] [2.6.12-rc2][suspend] Suspending Thinkpad: drive bay light in S3 mode stays on
Date: Mon, 11 Apr 2005 21:32:34 +0100	[thread overview]
Message-ID: <1113251554.10110.60.camel@tyrosine> (raw)
In-Reply-To: <20050411201741.73077.qmail@web88002.mail.re2.yahoo.com>

On Mon, 2005-04-11 at 16:17 -0400, Shawn Starr wrote:
> Sure, I suppose you can, but most suspend tools just
> echo stuff to /sys (or still /proc/acpi/sleep) which
> makes it harder to script it. Besides, when a laptop
> goes into suspend to RAM there should be no extra
> power   on except a Moon or some other icon.

Most suspend tools are depressingly stupid. That's not a good reason to
push functionality into the kernel. The vast majority of hardware won't
work with that approach at the moment.

> That said, the ACPI thinkpad extras was designed to do
> all of this so why shouldn't the driver do S3 suspend
> if it hooks into it already?

Because, well, strictly it wasn't. The LED control functionality in the
IBM-acpi code exists because it exposes methods that are used by the
BIOS in normal usage. It gives some degree of extra flexibility -
there's no point in removing that for the sake of having one fewer line
of shell in a suspend script. I might want the LEDs to be in different
states depending on what triggered the suspend.

-- 
Matthew Garrett | mjg59@srcf.ucam.org


  reply	other threads:[~2005-04-11 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-11 20:17 Shawn Starr
2005-04-11 20:32 ` Matthew Garrett [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-11 20:03 Shawn Starr
2005-04-11 20:14 ` [ACPI] " Matthew Garrett

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=1113251554.10110.60.camel@tyrosine \
    --to=mjg59@srcf.ucam.org \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawn.starr@rogers.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

all inboxes | Powered by JetHome®