From: Seth Forshee <seth.forshee@gmail.com>
To: linux-omap@vger.kernel.org
Subject: AUTO_EXTVOLT on OMAP2430
Date: Mon, 20 Oct 2008 00:07:26 -0500 [thread overview]
Message-ID: <20081020050726.GA12891@ubuntu-workstation> (raw)
I'm working with what basically amounts to an older version of the linux-omap
kernel with substantial modifications. I found that in some situations I was
getting about 4 mA more current draw during suspend than at other times. This
was ultimately being caused by some of the code that runs in SRAM masking off
the PRCM_VOLTCTRL[AUTO_EXTVOLT] bit. I compared to tips in the linux-omap repo
for comparison and found the situation is the same -- the bit is set during
initialization, but will be cleared by the SRAM code that configures the SDRC.
>From reading the TRM it seems that this bit should only affect the retention
and off states, so I don't understand why it needs to be masked during SDRC
configuration. Is there any danger in changing the mask to leave this bit
unchanged? Or would it be safer to set this bit before suspend and clear it
after?
Thanks,
Seth
reply other threads:[~2008-10-20 5:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20081020050726.GA12891@ubuntu-workstation \
--to=seth.forshee@gmail.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