linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Govindraj <govindraj.ti@gmail.com>,
	Jean Pihet <jean.pihet@newoldbits.com>,
	linux-omap@vger.kernel.org
Subject: Re: BeagleBoard not resuming from uart with latest pm-core ?
Date: Tue, 16 Nov 2010 14:59:30 -0800	[thread overview]
Message-ID: <87pqu4c1t9.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20101115151430.15c899e5@surf> (Thomas Petazzoni's message of "Mon, 15 Nov 2010 15:14:30 +0100")

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

> Hello Govindraj,
>
> On Mon, 15 Nov 2010 19:24:05 +0530
> Govindraj <govindraj.ti@gmail.com> wrote:
>
>> Can you check if you have below two patches in the kernel you have?
>> 
>> http://www.spinics.net/lists/linux-serial/msg02684.html
>> http://www.spinics.net/lists/linux-serial/msg02683.html
>> 
>> If not there can you check applying these two patch
>
> I have both of these patches in my kernel (I'm running the latest
> pm-core from Kevin's repository).

Hmm, using pm-core, I can hit full-chip retention in suspend on my
Beagle C4.

However, upgrading to a recent x-loader and u-boot, I can reproduce the
problem.

The problem is an old one that seems to have resurfaced.  Namely, u-boot
leaves the MUSB block in a state that prevents it from idling, and thus
prevents CORE from hitting RET.

I have a series of hacks for this in the PM branch (see my pm-otg-reset
branch) that fixes the problem, but is not clean.  This will work until
the omap_hwmod conversion for MUSB is done.   One of the perks we get
from omap_hwmod is that a reset is done for each hwmod ensuring that any
(mis)configuration of the bootloader is cleared and the HW is in a known
default state.

Kevin



  reply	other threads:[~2010-11-16 22:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 15:44 BeagleBoard not resuming from uart with latest pm-core ? Thomas Petazzoni
2010-11-10 16:07 ` Jean Pihet
2010-11-10 17:32   ` Kevin Hilman
2010-11-11 11:41     ` Peter 'p2' De Schrijver
2010-11-11 16:00       ` Kevin Hilman
2010-11-15 10:50     ` Thomas Petazzoni
2010-11-15 13:13       ` Thomas Petazzoni
2010-11-15 13:54         ` Govindraj
2010-11-15 14:14           ` Thomas Petazzoni
2010-11-16 22:59             ` Kevin Hilman [this message]
2010-11-17  7:20               ` Thomas Petazzoni
2010-11-15 19:29         ` Kevin Hilman

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=87pqu4c1t9.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=govindraj.ti@gmail.com \
    --cc=jean.pihet@newoldbits.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).