From: Tony Lindgren <tony@atomide.com>
To: Ran Shalit <ranshalit@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Fail to enter retention
Date: Mon, 17 Nov 2014 12:38:08 -0800 [thread overview]
Message-ID: <20141117203808.GH7046@atomide.com> (raw)
In-Reply-To: <CAJ2oMhL5x3nAxTQg36O9-DUfHK9iy-g9+qqN=bYj3Nw7HNjAnA@mail.gmail.com>
* Ran Shalit <ranshalit@gmail.com> [141117 11:48]:
> >You need to look if you have some devices blocking deeper
> >idle states in cm_idlest*_core and cm_idlest_per registers.
>
> >The device will automatically idle whatever it can if there
> >are no blockers. I believe at least EHCI still is blocking,
> >and MUSB if configured and cable connected.
>
> I'll check the registers value, should I then try to modify this
> registers in order to get into retention ?
No, those are read-only status registers. You need idle the
drivers that show as blocking in those registers.
> I will still have to disable serial right ? Maybe some kernel process
> which run in background prevents retention ?
Yes otherwise the UART bits will show as blocking in those
registers.
> Is there some simple way to debug this or do I need to modify these registers ?
Just printing them out in the idle loop most likely will give
you the info you need.
Regards,
Tony
next prev parent reply other threads:[~2014-11-17 20:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 20:10 Fail to enter retention Ran Shalit
2014-11-17 16:22 ` Tony Lindgren
2014-11-17 17:12 ` Ran Shalit
2014-11-17 18:09 ` Tony Lindgren
2014-11-17 19:46 ` Ran Shalit
2014-11-17 20:38 ` Tony Lindgren [this message]
2014-11-17 21:09 ` Ran Shalit
2014-11-18 8:21 ` Ran Shalit
2014-11-18 8:25 ` Ran Shalit
2014-11-18 15:45 ` Tony Lindgren
[not found] ` <CAJ2oMhJUNsKtP1VYF+6dWDfmAEF3qvfbN7ahhVBdDBgZt7thGA@mail.gmail.com>
2014-11-18 21:47 ` Ran Shalit
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=20141117203808.GH7046@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=ranshalit@gmail.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 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.