public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Michael Trimarchi <trimarchi@gandalf.sssup.it>
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: Tue, 7 Apr 2009 22:57:23 +0200	[thread overview]
Message-ID: <200904072257.23756.rjw@sisk.pl> (raw)
In-Reply-To: <49DBA319.3030008@gandalf.sssup.it>

On Tuesday 07 April 2009, Michael Trimarchi wrote:
> Rafael J. Wysocki wrote:
> > On Tuesday 07 April 2009, Michael Trimarchi wrote:
> >   
> >> Hi,
> >>
> >> Rafael J. Wysocki wrote:
> >>     
> >>> On Tuesday 07 April 2009, Michael Trimarchi wrote:
> >>>   
> >>>       
> >>>> This is a little rework of linux power scheme. TODO:
> >>>> - remove recursive call
> >>>> - clean-up code
> >>>>
> >>>> Avoid suspend of a device that is connected with other coprocessor
> >>>> like GSM chip.
> >>>>     
> >>>>         
> >>> Well, can you please tell us a bit about the motivation for this work?
> >>>
> >>> I don't like the approach, but I'd like to know what you're trying to achieve.
> >>>   
> >>>       
> >> I works on an hardware that have the gsm connect to wm8753 and the 
> >> bluetooth subsystem
> >> too direct connected. So I would like that a phone call for example 
> >> remains on during
> >> system suspend. With this approch I can disable suspend of an entire 
> >> subtree of device,
> >> that can be used by other hardware component. This change avoid any 
> >> specific change to the
> >> driver.
> >>     
> >
> > Why do you want to avoid changing the driver, actually?
> >
> > Rafael
> >
> >   
> Because, the driver may be connected to other device and you must change 
> the entire
> set. This simple modification can help to share devices on an embedded 
> board and control
> suspend/resume enable from user space. I don't know if it can be usefull 
> on broken board/device too. Do you see any possible risk with this 
> change?

Yes, a (rather high) risk of abuse.

> When I write it I try to have a simple modification on linux-pm part.

So, basically, you'd like to introduce an interface allowing the user space to
tell the kernel which devices not to suspend, because there may be some
dependencies between devices that the kernel presumably doesn't know of.

Well, what about teaching these dependencies to the kernel, so that it
can take them into account by itself?

Rafael

  parent reply	other threads:[~2009-04-07 20:57 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 [this message]
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
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=200904072257.23756.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=trimarchi@gandalf.sssup.it \
    /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