From: Borislav Petkov <petkovbb@googlemail.com>
To: Peter Feuerer <peter@piie.net>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
lenb@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] acerhdf: convert to dev_pm_ops
Date: Tue, 28 Jul 2009 11:08:19 +0200 [thread overview]
Message-ID: <9ea470500907280208v1d8140b5v9d7d7f09df8f060f@mail.gmail.com> (raw)
In-Reply-To: <cone.1248765902.464745.15136.1000@arca>
Hi,
On Tue, Jul 28, 2009 at 9:25 AM, Peter Feuerer<peter@piie.net> wrote:
[..]
>>> Hmm, looking at the driver I think the only function that actually
>>> is needed is poweroff() that would turn the fan in automatic mode
>>> before shutting down. The driver does not perform any actions when
>>> resuming so why bother?
>>
>> Agreed.
>>
>> Also, the fan comes out of warm and cold reboot in mode AUTO and
>> when the driver is enabled, the fan is turned off on the next run of
>> thermal_zone_device_update() when the read out temperature is within
>> limits.
>>
>> Correct me if I'm wrong, but the only reason I see for setting the
>> fan to mode AUTO before suspending/hibernating/etc is if it is taking
>> a really long time to hibernate and write RAM image to disk and the
>> machine is getting hot during that process. Otherwise, we might just
>> as well do _nothing_ when suspending and remove all suspend/resume
>> functionality altogether, no?
>
> This is right, currently the only reason for calling the suspend /
> hibernate functions is to set the fan to auto to ensure it doesn't get
> too hot while the kernel prepares the machine to suspend / hibernate.
>
> I would like to keep the resume function too. It's a nice to see
> what's happening with verbose=1.
That's not a reason for keeping code in the kernel and raising bloat
levels unnecessarily. If the driver doesn't need to do anything on
resume, then no function is needed.
--
Regards/Gruss,
Boris
next prev parent reply other threads:[~2009-07-28 9:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 15:48 Borislav Petkov
2009-07-15 18:36 ` Peter Feuerer
2009-07-23 8:29 ` Dmitry Torokhov
2009-07-23 8:52 ` Peter Feuerer
2009-07-23 9:21 ` Borislav Petkov
2009-07-23 12:53 ` Borislav Petkov
2009-07-27 9:07 ` Peter Feuerer
2009-07-27 15:55 ` Dmitry Torokhov
2009-07-27 18:37 ` Borislav Petkov
2009-07-28 7:25 ` Peter Feuerer
2009-07-28 9:08 ` Borislav Petkov [this message]
2009-07-28 13:25 ` Peter Feuerer
2009-07-28 13:59 ` Borislav Petkov
2009-07-29 7:25 ` Peter Feuerer
2009-07-29 11:55 ` Borislav Petkov
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=9ea470500907280208v1d8140b5v9d7d7f09df8f060f@mail.gmail.com \
--to=petkovbb@googlemail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@piie.net \
/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®