mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: MyungJoo Ham <myungjoo.ham@samsung.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	linux-pm@lists.linux-foundation.org,
	Len Brown <len.brown@intel.com>,
	"Jean Delvare (PC drivers core)" <khali@linux-fr.org>,
	"Ben Dooks (embedded platforms)" <ben-linux@fluff.org>,
	kyungmin.park@samsung.com, myungjoo.ham@gmail.com,
	LKML <linux-kernel@vger.kernel.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	rpurdie@rpsys.net, lenz@cs.wisc.edu, arminlitzel@web.de,
	Cyril Hrubis <metan@ucw.cz>,
	thommycheck@gmail.com,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	dbaryshkov@gmail.com, omegamoon@gmail.com, eric.y.miao@gmail.com,
	utx@penguin.cz, zaurus-devel@www.linuxtogo.org,
	Marek Vasut <marek.vasut@gmail.com>
Subject: Re: [RFC PATCH v2 1/3] PM / Core: suspend_again callback for device PM.
Date: Wed, 27 Apr 2011 00:10:54 +0200	[thread overview]
Message-ID: <20110426221054.GB29092@elf.ucw.cz> (raw)
In-Reply-To: <201104262346.58046.rjw@sisk.pl>

Hi!

> > > And that's exactly what should be done.  Have a user space process controlling
> > > that, because avoiding to thaw user space doesn't buy us almost
> > > anything.
> > 
> > That makes Zaurus implement different user-kernel interface than PC
> > class machine, because of hardware quirk.
> 
> Let me say that again: If Zaurus needs to resume everything except for
> user space periodically to monitor the battery charger, I'm not sure if our
> suspend interface is the right one for it in the first place.

Well, Zaurus does not need to resume everything. SPI+charger code is
enough, and that would be preffered. No need to touch disk etc.

> It seriously looks like a workaround for the lack of appropriately implemented
> runtime PM, just like the Android's opportunistic suspend.

No, not really. I'm running standard Debian; I do not want/need
anything like opportunistic suspend.

> > > Now, I know that it's probably easier to modify the kernel than to write
> > > a user space tool for that, test it and so on, but "easier" is not necessarily
> > > "better".
> > 
> > It is easier, allows us to keep same user-kernel interface on PC and
> > Zaurus, and is compatible with 2.6.38.
> > 
> > Heck, I'm used to typing "echo mem > /sys/power/state". I should not
> > have to learn different interface just because Zaurus does not have
> > proper hardware charger.
> 
> No, this interface should not be used on Zaurus at all.  It's not mean for
> that and while you can hack it to kind of work, it still is hacking rather
> than designing things.

Why not? I want the Zaurus to sleep. Why should I have to know how its
charging unit works? Why should I use different interface than on PC?
I want it to suspend, put it into backpack and move...

> > Bootloader takes care of battery in that case.
> 
> So the difference is that we let someone else worry.  Cool. :-)

Yes.

> > Ok, see the spitz_should_wakeup() function in arch/arm/mach-pxa/* and
> > should_wakeup() usage.
> 
> OK, I will.

Thanks.
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2011-04-26 22:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20  8:28 [RFC PATCH] PM / Core: suspend_again cb for syscore_ops MyungJoo Ham
2011-04-20 10:36 ` Pavel Machek
2011-04-20 20:28 ` Rafael J. Wysocki
2011-04-21  7:03   ` MyungJoo Ham
     [not found] ` <1303781471-2477-1-git-send-email-myungjoo.ham@samsung.com>
2011-04-26 11:47   ` [RFC PATCH v2 1/3] PM / Core: suspend_again callback for device PM Rafael J. Wysocki
2011-04-26 13:17     ` Greg KH
2011-04-26 20:38       ` Pavel Machek
2011-04-26 20:49         ` Rafael J. Wysocki
2011-04-26 21:11           ` Pavel Machek
2011-04-26 21:36             ` Rafael J. Wysocki
2011-04-26 22:06               ` Pavel Machek
2011-04-26 20:57         ` Greg KH
2011-04-26 22:14           ` Pavel Machek
2011-04-26 20:35     ` Pavel Machek
2011-04-26 20:47       ` Rafael J. Wysocki
2011-04-26 21:06         ` Pavel Machek
2011-04-26 21:46           ` Rafael J. Wysocki
2011-04-26 22:10             ` Pavel Machek [this message]
2011-04-26 22:32             ` Rafael J. Wysocki
2011-04-27  6:36               ` MyungJoo Ham
2011-04-27  9:46                 ` Stanislav Brabec
2011-04-27 10:47                   ` MyungJoo Ham

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=20110426221054.GB29092@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=arminlitzel@web.de \
    --cc=ben-linux@fluff.org \
    --cc=dbaryshkov@gmail.com \
    --cc=eric.y.miao@gmail.com \
    --cc=gregkh@suse.de \
    --cc=khali@linux-fr.org \
    --cc=kyungmin.park@samsung.com \
    --cc=len.brown@intel.com \
    --cc=lenz@cs.wisc.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=marek.vasut@gmail.com \
    --cc=metan@ucw.cz \
    --cc=myungjoo.ham@gmail.com \
    --cc=myungjoo.ham@samsung.com \
    --cc=omegamoon@gmail.com \
    --cc=rjw@sisk.pl \
    --cc=rpurdie@rpsys.net \
    --cc=stern@rowland.harvard.edu \
    --cc=thommycheck@gmail.com \
    --cc=utx@penguin.cz \
    --cc=zaurus-devel@www.linuxtogo.org \
    /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®