From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Reddy, Teerth" <teerth@ti.com>
Cc: "V, Hemanth" <hemanthv@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: PM branch update: rebase to .31-rc, added omap_hwmod/omap_device
Date: Thu, 13 Aug 2009 06:03:51 -0700 [thread overview]
Message-ID: <873a7voog8.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB0306050777@dbde02.ent.ti.com> (Teerth Reddy's message of "Thu\, 13 Aug 2009 11\:30\:57 +0530")
"Reddy, Teerth" <teerth@ti.com> writes:
> I did some testing with the current PM branch and don't see this issue on SDP.
Thanks for testing.
> I could not find the patch which fixes this issue. Can you please
> point us to the patch which fixes this issue?
To be honest, I actually don't know which patch fixed the issue. I saw the
problem during some early testing of the latest PM branch, and in the process
of restructuring the tree it went away.
More than likely, I had left out part of the series when reorganizing
that caused this temporary problem.
I think I'll remove it from the 'known problems' list as it appears to
have been operator error on my part.
Kevin
>
> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Kevin Hilman
> Sent: Wednesday, August 12, 2009 8:28 PM
> To: V, Hemanth
> Cc: linux-omap@vger.kernel.org
> Subject: Re: PM branch update: rebase to .31-rc, added omap_hwmod/omap_device
>
> "Hemanth V" <hemanthv@ti.com> writes:
>
>> ----- Original Message -----
>> From: "Kevin Hilman" <khilman@deeprootsystems.com>
>>> Known problems:
>>
>>> - network drivers and off-mode
>>> - various hangs when using off-while-idle and NFS-mounted rootfs
>>> - network drivers likely need some context save/restore support
>>
>> Kevin, was this known to work earlier. Could this be related to
>> GPMC context save/restore.
>
> I wrote this based on some early testing of the latest PM branch,
> where I may of still had some bugs. But I also have not seen
> this in a while, so it may have been just a problem when I was
> reworking/reordering the context save/restore code.
>
> I decided to leave it in the 'known problems' list in case anyone else
> has seen it and because I didn't go back and re-test all the boards
> for this issue.
>
> I don't see any issues on SDP or EVM anymore, have you tested the
> current PM branch for this?
>
> Kevin
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-08-13 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 0:19 PM branch update: rebase to .31-rc, added omap_hwmod/omap_device Kevin Hilman
2009-08-12 14:37 ` Hemanth V
2009-08-12 14:58 ` Kevin Hilman
2009-08-13 6:00 ` Reddy, Teerth
2009-08-13 13:03 ` 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=873a7voog8.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=hemanthv@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=teerth@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox