From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: pHilipp Zabel <philipp.zabel@gmail.com>
Cc: Daniel Mack <daniel@caiaq.de>, Frans Pop <elendil@planet.nl>,
linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org, spyro@f2s.com, cbou@mail.ru,
mreimer@vpop.net
Subject: Re: [PATCH 2/5] pda-power: switch to new dev_pm_ops
Date: Fri, 4 Sep 2009 20:34:04 +0400 [thread overview]
Message-ID: <20090904163404.GA26581@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <74d0deb30908070635s2fa76e5t954742239b8592a4@mail.gmail.com>
On Fri, Aug 07, 2009 at 03:35:19PM +0200, pHilipp Zabel wrote:
[...]
> > +static struct dev_pm_ops pda_power_pm_ops = {
> > + .poweroff = pda_power_poweroff,
> > + .restore = pda_power_restore,
> > +};
>
> No no, now you're missing .suspend/.resume. As I understand it, the
> suspend and hibernation codepaths are now completely separate.
>
> Also, I'm not sure using .restore here is quite correct.
> enable_irq_wake is called in .poweroff, after .freeze + creation of
> the memory image. So if this memory image is restored during the next
> boot, there is no trace of irq wakup ever being enabled and thus no
> need to call disable_irq_wake.
>
> I think just .suspend/.poweroff and .resume need to be used for this driver.
Daniel, any update on this patch?
Thanks,
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2009-09-04 16:34 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 18:29 [PATCH 1/5] w1_gpio: switch to new dev_pm_ops Daniel Mack
2009-08-05 18:29 ` [PATCH 2/5] pda-power: " Daniel Mack
2009-08-05 18:29 ` [PATCH 3/5] ds2760: " Daniel Mack
2009-08-05 18:29 ` [PATCH 4/5] input: gpio-keys: " Daniel Mack
2009-08-05 18:29 ` Daniel Mack
2009-08-05 18:29 ` [PATCH 5/5] net: smsc911x: " Daniel Mack
2009-08-05 18:29 ` Daniel Mack
2009-08-06 3:29 ` David Miller
2009-08-06 3:29 ` David Miller
2009-08-06 11:53 ` Steve.Glendinning
2009-08-06 11:53 ` Steve.Glendinning
2009-08-06 11:53 ` Steve.Glendinning
2009-08-06 20:26 ` David Miller
2009-08-06 20:26 ` David Miller
2009-08-06 20:26 ` David Miller
2009-08-05 20:15 ` [PATCH 4/5] input: gpio-keys: " pHilipp Zabel
2009-08-05 20:15 ` pHilipp Zabel
2009-08-05 22:33 ` Daniel Mack
2009-08-05 22:33 ` Daniel Mack
2009-08-06 0:51 ` [linux-pm] " Rafael J. Wysocki
2009-08-06 12:59 ` Daniel Mack
2009-08-06 15:19 ` Rafael J. Wysocki
2009-08-07 13:39 ` pHilipp Zabel
2009-08-07 13:39 ` [linux-pm] " pHilipp Zabel
2009-08-07 13:39 ` pHilipp Zabel
2009-08-06 15:19 ` Rafael J. Wysocki
2009-08-06 12:59 ` Daniel Mack
2009-08-06 0:51 ` Rafael J. Wysocki
2009-08-05 20:15 ` pHilipp Zabel
2009-08-05 18:29 ` [PATCH 3/5] ds2760: " Daniel Mack
2009-08-05 19:49 ` [PATCH 2/5] pda-power: " Frans Pop
2009-08-05 19:49 ` Frans Pop
2009-08-05 22:29 ` Daniel Mack
2009-08-06 11:52 ` pHilipp Zabel
2009-08-06 11:52 ` pHilipp Zabel
2009-08-06 12:56 ` Daniel Mack
2009-08-07 13:35 ` pHilipp Zabel
2009-09-04 16:34 ` Anton Vorontsov [this message]
2009-09-04 16:34 ` Anton Vorontsov
2009-08-07 13:35 ` pHilipp Zabel
2009-08-06 12:56 ` Daniel Mack
2009-08-05 22:29 ` Daniel Mack
2009-08-05 18:29 ` Daniel Mack
2009-08-05 18:44 ` [PATCH 1/5] w1_gpio: " Rafael J. Wysocki
2009-08-05 18:44 ` Rafael J. Wysocki
2009-08-05 18:45 ` Daniel Mack
2009-08-05 18:45 ` Daniel Mack
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=20090904163404.GA26581@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=cbou@mail.ru \
--cc=daniel@caiaq.de \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mreimer@vpop.net \
--cc=philipp.zabel@gmail.com \
--cc=spyro@f2s.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.