From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Suspend to RAM broken on BeagleBoard ?
Date: Sat, 11 Sep 2010 11:00:07 +0200 [thread overview]
Message-ID: <20100911110007.5f7b529d@surf> (raw)
In-Reply-To: <87sk1h4640.fsf@deeprootsystems.com>
On Fri, 10 Sep 2010 14:54:23 -0700
Kevin Hilman <khilman@deeprootsystems.com> wrote:
> It's the CPUfreq driver that's failing to suspend.
Ok.
> Yes, CPUfreq is not supported in l-o master or pm-core (only in the
> full pm branch.) If you Kconfig out CPUfreq, this failure will go
> away.
Aah, yes, I forgot about this. I know it's temporary, but wouldn't it
be good to disable CPUfreq in omap3_defconfig in this case ?
BTW, I'm now seeing:
[ 37.830596] Powerdomain (core_pwrdm) didn't enter target state 1
[ 37.830627] Powerdomain (dss_pwrdm) didn't enter target state 1
when the system is woken up.
Concerning the USB issue, no idea ?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-09-11 9:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 15:48 Suspend to RAM broken on BeagleBoard ? Thomas Petazzoni
2010-09-10 17:00 ` Felipe Balbi
2010-09-10 18:47 ` Thomas Petazzoni
2010-09-11 14:21 ` Felipe Balbi
2010-09-10 21:54 ` Kevin Hilman
2010-09-11 9:00 ` Thomas Petazzoni [this message]
2010-09-13 14:56 ` Kevin Hilman
2010-09-13 15:39 ` Thomas Petazzoni
2010-09-13 16:25 ` Grazvydas Ignotas
2010-09-13 19:01 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2010-09-10 20:28 msinger
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=20100911110007.5f7b529d@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.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.