All of lore.kernel.org
 help / color / mirror / Atom feed
From: sebastian.capella@linaro.org (Sebastian Capella)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-pm] ARM hibernation / suspend-to-disk
Date: Tue, 28 Jan 2014 10:22:45 -0800	[thread overview]
Message-ID: <20140128182245.18840.51279@capellas-linux> (raw)
In-Reply-To: <20140128141458.GD8713@xo-6d-61-c0.localdomain>

Quoting Pavel Machek (2014-01-28 06:14:58)
> > > what's the status of suspend-to-disk on ARM? The most recent discussion I
> > > found is:
> > > http://lists.linuxfoundation.org/pipermail/linux-pm/2012-November/034997.html
> > > 
> > > with no replies at all. Is anyone still working on that? Anyone got it running?

Hi Pavel, Russ,

I have been looking and working with Russ' most recent branch based
on the 3.12 kernel, which includes the big pile of patches for OMAP.
(https://github.com/russdill/linux/commits/arm-hibernation-am33xx-v3.12)

He has hibernation mostly working and I have been able to run 1400 or
so entry/exits overnight there on beaglebone black without issue.
Combining this with device activity has been tricky.  An active
network will lose the link on restore.  Active SD traffic will
eventually hang (Last night ran for about 11 hours before hanging
after ~350 or so hibernations).  I have not found where this is or
the cause.

> > For ARM hibernation support to get merged, there needs to be at least
> > one platform that supports it. the am335x code I have is not ready as it
> > still relies on PM patchsets that have not yet themselves been merged.
> 
> Given that we have chicken-and-egg problem here, I believe it makes sense
> to merge generic ARM hibernation support now.

If you want to go ahead with upstreaming the base patch, Russ, would you
like me to do that for you or will you have time to do this?

Otherwise, I am still looking at how to get this upstream by verifying
on omap 5.  In my case, I still have the chicken egg problem, where I'm 
trying to verify on omap 5 with out of tree patches.

Thanks,

Sebastian

  reply	other threads:[~2014-01-28 18:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29  8:10 ARM hibernation / suspend-to-disk Jan Glauber
2013-05-29  8:25 ` [linux-pm] " Viresh Kumar
2013-05-29 17:23 ` Russ Dill
2014-01-28 14:14   ` [linux-pm] " Pavel Machek
2014-01-28 18:22     ` Sebastian Capella [this message]
2014-01-28 18:30       ` Sebastian Capella
2014-01-30 18:06       ` Pavel Machek
2014-01-30 18:27         ` Sebastian Capella
2014-02-16 13:11       ` TonyHo
2014-02-24 21:54         ` Sebastian Capella
2014-03-02  7:57           ` tonyho
2014-03-04  5:12             ` Sebastian Capella
2014-03-04 11:04               ` TonyHo
2014-03-05  0:16                 ` Sebastian Capella
2016-01-11 16:43                   ` Johann

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=20140128182245.18840.51279@capellas-linux \
    --to=sebastian.capella@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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 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.