From: tomi.valkeinen@ti•com (Tomi Valkeinen)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: dts: omap5-igep0050: Correct hdmi regulator
Date: Mon, 9 May 2016 11:34:38 +0300 [thread overview]
Message-ID: <57304B9E.50201@ti.com> (raw)
In-Reply-To: <a6969765-d07d-6d0e-36df-b78b485d9644@ti.com>
On 09/05/16 11:25, Peter Ujfalusi wrote:
> Tomi: what do you think?
>
> According to the OMAP5 data manual the vdda_hdmi can be in 1.5V or 1.8V mode,
> 2V is not mentioned in the recommended operating conditions table.
I thought vdda_hdmi should always be 1.8V, but you're right, on omap5
1.5V is allowed according to DM. On later SoCs it's only 1.8V. I suggest
we use 1.8V on all boards, as that's what's known to work.
2V is definitely wrong.
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160509/d962752c/attachment-0001.sig>
next prev parent reply other threads:[~2016-05-09 8:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 10:21 [PATCH] ARM: dts: omap5-igep0050: Correct hdmi regulator Peter Ujfalusi
2016-04-29 10:22 ` Peter Ujfalusi
2016-05-04 17:26 ` Tony Lindgren
2016-05-04 18:01 ` Nishanth Menon
2016-05-05 18:46 ` Tony Lindgren
2016-05-09 8:25 ` Peter Ujfalusi
2016-05-09 8:34 ` Tomi Valkeinen [this message]
[not found] ` <2822D1C2B9B19F4A8261F756A13373F801BEF7B4@DFLE11.ent.ti.com>
[not found] ` <CAPjucKb+4vd8Ar3MATCuTx+9R36PeB0hbvwDaAD1KTZFCiVJEA@mail.gmail.com>
[not found] ` <2822D1C2B9B19F4A8261F756A13373F801BF86D2@DFLE11.ent.ti.com>
[not found] ` <2822D1C2B9B19F4A8261F756A13373F801BF8703@DFLE11.ent.ti.com>
[not found] ` <CAPjucKb2PLSZcD3YZ9xQk1F62ugFaGAkBBqMp5GmoWFd0H8Vfg@mail.gmail.com>
2016-05-12 16:57 ` Tony Lindgren
2016-05-12 19:19 ` Nishanth Menon
2016-05-12 20:26 ` Tony Lindgren
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=57304B9E.50201@ti.com \
--to=tomi.valkeinen@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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