From: Michael Trimarchi <trimarchi@gandalf.sssup.it>
To: Nigel Cunningham <ncunningham@crca.org.au>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: [RFC Disable suspend on a specific device] This is a little change in linux power scheme
Date: Wed, 08 Apr 2009 07:59:06 +0200 [thread overview]
Message-ID: <49DC3D2A.1020405@gandalf.sssup.it> (raw)
In-Reply-To: <1239143110.7183.56.camel@nigel-laptop>
Hi,
Nigel Cunningham wrote:
> Hi.
>
> On Tue, 2009-04-07 at 23:38 +0200, Pavel Machek wrote:
>> Well.... userspace should not have to decide this. If userspace tells
>> kernel not to suspend video card (on PC/ACPI), then we either honour
>> the request, or violate ACPI spec (and probably break suspend).
>
> What about the cases where the ACPI spec is irrelevant? (As I understand
> it, not all embedded boards use ACPI). Would this be a good approach in
> those cases? If so, perhaps the trick would be to make the functionality
> depend on !CONFIG_ACPI?
It can be an option, or just add only in embedded configuration where is
not ACPI configured.
The dependences is allready provided by the kernel. The default is to
have suspend enabled.
The user level access it's needed because the kernel does't exacly know
when the device
must remain on/off during suspend. This api change can't cover any
possible scenario but
introduce a flexbility scheame in suspend process. Avoid suspend in some
device can be obtain
looking at dependece too? I don't know exacly if the acpi capapiblity
can be seen throw the
link to a bus or a specific class, but we can limit it to the platform
device instead
all device.
Michael
>
> Regards,
>
> Nigel
>
> _______________________________________________
> linux-pm mailing list
> linux-pm@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/linux-pm
>
next prev parent reply other threads:[~2009-04-08 5:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 10:29 [RFC Disable suspend on a specific device] This is a little change in linux power scheme Michael Trimarchi
2009-04-07 13:45 ` Rafael J. Wysocki
2009-04-07 15:39 ` Michael Trimarchi
2009-04-07 18:55 ` Rafael J. Wysocki
2009-04-07 19:01 ` Michael Trimarchi
2009-04-07 20:40 ` Pavel Machek
2009-04-07 20:57 ` Rafael J. Wysocki
2009-04-07 21:31 ` Alan Stern
2009-04-07 21:38 ` Pavel Machek
2009-04-07 22:25 ` Nigel Cunningham
2009-04-08 5:59 ` Michael Trimarchi [this message]
2009-04-08 8:13 ` Rafael J. Wysocki
2009-04-08 8:24 ` Michael Trimarchi
2009-04-08 8:34 ` Rafael J. Wysocki
2009-04-08 8:45 ` Michael Trimarchi
2009-04-07 8:06 ` Pavel Machek
2009-04-20 12:46 ` Mark Brown
2009-04-20 12:55 ` Michael Trimarchi
2009-04-08 11:42 ` Mark Brown
2009-04-08 16:44 ` Igor Stoppa
2009-04-08 18:23 ` Mark Brown
2009-04-08 19:53 ` Igor Stoppa
2009-04-09 14:33 ` Mark Brown
2009-04-07 21:40 ` Rafael J. Wysocki
2009-04-08 11:53 ` Mark Brown
2009-04-08 16:45 ` Igor Stoppa
2009-04-10 11:17 ` Pavel Machek
2009-04-08 20:37 ` Alan Stern
2009-04-08 21:25 ` Michael Trimarchi
2009-04-08 21:56 ` Rafael J. Wysocki
2009-04-09 18:27 ` Alan Stern
2009-04-09 22:33 ` Rafael J. Wysocki
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=49DC3D2A.1020405@gandalf.sssup.it \
--to=trimarchi@gandalf.sssup.it \
--cc=linux-pm@lists.linux-foundation.org \
--cc=ncunningham@crca.org.au \
/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