From: Patrick <kpa_info@yahoo.fr>
To: linux-omap@vger.kernel.org
Subject: OMAP4 TWL6030 uv_to_vsel warning
Date: Tue, 03 Apr 2012 16:27:57 +0200 [thread overview]
Message-ID: <4F7B08ED.1060104@yahoo.fr> (raw)
Dear mailing-list,
I am working with the 3.3 kernel on an OMAP4430 with a TWL6030.
I have many warning like the following:
twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660
I would like to clarify this and eventually "remove" this warning.
I have checked omap_twl.c file. It seems that twl6030_uv_to_vsel()
function have a special branch when uv is equal to 1350000 uV and when
bigger than 1350000 uV it print the error message.
On the same file I could see that on_volt (and the onlp_volt) are set by
default to 1375000 uV for the OMAP4.
On the datasheet of the TWL6030 I could see that the level is 1367400
uV. 1350000 nor than 1375000 are invalid level.
Don't you thin that 1375000 and 1350000 should be the same value ?
If we could change the default on_volt (and the onlp_volt) for the OMAP4
to 1350000 the Warning message will then be removed, and the effective
level on the TWL6030 will still stay to 1367400 uV.
Any comment are welcome !
Patrick
reply other threads:[~2012-04-03 14:34 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=4F7B08ED.1060104@yahoo.fr \
--to=kpa_info@yahoo.fr \
--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;
as well as URLs for NNTP newsgroup(s).