From: frank.hofmann@tomtom.com (Frank Hofmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [TuxOnIce-devel] [RFC PATCH] Current status, suspend-to-disk support on ARM
Date: Tue, 19 Apr 2011 19:13:07 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.00.1104191859260.4937@localhost6.localdomain6> (raw)
In-Reply-To: <BANLkTinroLCypX-iG0xGpnyxBk=P5TVtJQ@mail.gmail.com>
On Mon, 18 Apr 2011, Matt Hsu wrote:
>>
>>
>> The last thing here in my setup that's obviously not correctly suspending /
>> resuming is the OMAP display driver; I'm not the only one with that problem,
>> Matt's previous report:
>>
>> http://blog.gmane.org/gmane.linux.swsusp.devel/month=20101201
>>
>> has the same thing, "omapdss DISPC error: SYNC_LOST, disabling LCD".
>>
>>
>> Hi FrankH,
>
> Above issue could be resolved by:
Thanks Matt.
It didn't do the trick for me, but then a solution was found; we were
using the omap dss vrfb component and that didn't resume properly (not
from ram, nor from disk). We've disabled it and behold, screen comes back
now ;-)
New patch set once I've done a bit more testing. I've found a way to use
swapper_pg_dir (i.e. should allow for uswsusp - how would I test that ?)
that seems to do the job on OMAP as well, but I'd rather validate
thoroughly.
Also, I'd like to investigate whether ARM will require a set of
platform_hibernation_ops - Samsung's patch from last December,
http://www.spinics.net/lists/arm-kernel/msg108565.html
seems to indicate that they believe it's necessary at least on some ARM
hardware. OMAP has similar functions to that, it'd be great to unify.
FrankH.
>
> - CONFIG_FB_OMAP2_FORCE_AUTO_UPDATE=y
> - the following patch
>
> diff --git a/drivers/video/omap2/dss/dispc.c
> b/drivers/video/omap2/dss/dispc.c
> index 8b3ac80..a188732 100644
> --- a/drivers/video/omap2/dss/dispc.c
> +++ b/drivers/video/omap2/dss/dispc.c
> @@ -2784,7 +2784,6 @@ static void dispc_error_worker(struct work_struct
> *work)
> bool enable = false;
>
> DSSERR("SYNC_LOST, disabling LCD\n");
>
> for (i = 0; i < omap_dss_get_num_overlay_managers(); ++i) {
> struct omap_overlay_manager *mgr;
> mgr = omap_dss_get_overlay_manager(i);
> @@ -2815,6 +2814,9 @@ static void dispc_error_worker(struct work_struct
> *work)
> if (enable)
> manager->device->enable(manager->device);
> }
> +
> + dispc_enable_lcd_out(false);
> + dispc_enable_lcd_out(true);
>
> Although this patch is somehow nasty, but it work anyway.
>
> - Matt
>
next prev parent reply other threads:[~2011-04-19 18:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 14:47 [RFC PATCH] Current status, suspend-to-disk support on ARM Frank Hofmann
2011-04-04 15:06 ` Frank Hofmann
2011-04-05 12:22 ` [RFC PATCH v2] " Frank Hofmann
2011-04-12 5:59 ` [RFC PATCH] " Pavel Machek
2011-04-12 16:30 ` Frank Hofmann
2011-04-12 18:32 ` Pavel Machek
2011-04-13 13:36 ` Frank Hofmann
2011-04-13 21:38 ` Rafael J. Wysocki
2011-04-14 17:06 ` Frank Hofmann
2011-04-18 5:48 ` [TuxOnIce-devel] " Matt Hsu
2011-04-19 18:13 ` Frank Hofmann [this message]
2011-04-20 7:14 ` Matt Hsu
2011-04-21 4:55 ` [linux-pm] " MyungJoo Ham
-- strict thread matches above, loose matches on Subject: below --
2011-04-04 15:41 john at johnandjuliet.com
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=alpine.DEB.2.00.1104191859260.4937@localhost6.localdomain6 \
--to=frank.hofmann@tomtom.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox