From: Kevin Hilman <khilman@deeprootsystems.com>
To: Elvis Dowson <elvis.dowson@mac.com>
Cc: Linux OMAP Users <linux-omap@vger.kernel.org>
Subject: Re: Does SmartReflex pm patches affect USB suspend resume operations
Date: Tue, 19 May 2009 09:22:21 -0700 [thread overview]
Message-ID: <87my996p1e.fsf@deeprootsystems.com> (raw)
In-Reply-To: <519CDA29-3736-4123-A8A7-7BA613AE342C@mac.com> (Elvis Dowson's message of "Tue\, 19 May 2009 20\:16\:23 +0400")
Elvis Dowson <elvis.dowson@mac.com> writes:
> Hi Kevin,
>
> On May 19, 2009, at 8:12 PM, Kevin Hilman wrote:
>>>
>>
>> You're testing something that others are not: PM branch minus SR
>> patches.
>>
>> I suggest you re-add the SR patches and try the suggestions of others:
>> Roger's patches + fix your board file.
>
> I've just finished the board-overo.c modifications and will try the SR
> patches now.
>
> I try it first without Roger's modifications and see what happens, and
> then apply his modifications.
>
>> That being said, the USB driver is known to be not fully PM aware yet.
>> On my SDP, I've tested MUSB in host mode with mass storage and a USB
>> key and it can suspend/resume just fine. However, it does not work
>> with off-mode.
>
> What is off-mode?
>
Off-mode is when most of the chip goes off during suspend/idle. This
requires some driver support which is missing in many of the drivers since
if the chip goes off, the driver needs to save/restore state.
Off-mode is disabled by default on the PM branch, but can be enabled
by doing
# echo 1 > /sys/power/enable_off_mode
Kevin
prev parent reply other threads:[~2009-05-19 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7B1B64C5-631E-4C63-B1F3-F4429C697614@mac.com>
2009-05-19 16:12 ` Does SmartReflex pm patches affect USB suspend resume operations Kevin Hilman
[not found] ` <519CDA29-3736-4123-A8A7-7BA613AE342C@mac.com>
2009-05-19 16:22 ` Kevin Hilman [this message]
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=87my996p1e.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=elvis.dowson@mac.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox