From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: "Eduard Gavin" <egavin@iseebcn.com>,
"Enric Balletbo i Serra" <eballetbo@iseebcn.com>,
"Agustí Fontquerni" <af@iseebcn.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: omap5-igep0050: Correct hdmi regulator
Date: Thu, 12 May 2016 13:26:57 -0700 [thread overview]
Message-ID: <20160512202656.GU5995@atomide.com> (raw)
In-Reply-To: <5734D733.9060400@ti.com>
* Nishanth Menon <nm@ti.com> [160512 12:21]:
> On 05/12/2016 11:57 AM, Tony Lindgren wrote:
> > + * LDO7 is used for HDMI: VDDA_DSIPORTA - ball AA33, VDDA_DSIPORTC - ball AE33
> > + * VDDA_HDMI - ball AN25. LDO4 is: VPP1 - ball AD9.
>
> We should set ldo4_reg as 2v as well (default in omap5-board-common is
> 1.8v). VPP1 should be 2v to prevent efuse from being messed up.
Oh OK, here's the patch updated for ldo4.
Tony
8< --------------------
From: Tony Lindgren <tony@atomide.com>
Date: Thu, 12 May 2016 09:51:51 -0700
Subject: [PATCH] ARM: dts: Fix ldo7 source for HDMI on igepv5
Fix ldo7 source for HDMI on igepv5.
Suggested-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
--- a/arch/arm/boot/dts/omap5-igep0050.dts
+++ b/arch/arm/boot/dts/omap5-igep0050.dts
@@ -35,6 +35,22 @@
};
};
+/* LDO4 is VPP1 - ball AD9 */
+&ldo4_reg {
+ regulator-min-microvolt = <2000000>;
+ regulator-max-microvolt = <2000000>;
+};
+
+/*
+ * LDO7 is used for HDMI: VDDA_DSIPORTA - ball AA33, VDDA_DSIPORTC - ball AE33,
+ * VDDA_HDMI - ball AN25
+ */
+&ldo7_reg {
+ status = "okay";
+ regulator-min-microvolt = <1800000>;
+ regulator-max-microvolt = <1800000>;
+};
+
&omap5_pmx_core {
i2c4_pins: pinmux_i2c4_pins {
pinctrl-single,pins = <
prev parent reply other threads:[~2016-05-12 20:26 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
[not found] ` <1461925297-9734-1-git-send-email-peter.ujfalusi-l0cyMroinI0@public.gmane.org>
2016-04-29 10:22 ` Peter Ujfalusi
[not found] ` <6ee9d67a-e907-715a-f3f5-d90a470314c3-l0cyMroinI0@public.gmane.org>
2016-05-04 17:26 ` Tony Lindgren
2016-05-04 18:01 ` Nishanth Menon
[not found] ` <572A38FD.9050801-l0cyMroinI0@public.gmane.org>
2016-05-05 18:46 ` Tony Lindgren
2016-05-09 8:25 ` Peter Ujfalusi
2016-05-09 8:34 ` Tomi Valkeinen
[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 [this message]
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=20160512202656.GU5995@atomide.com \
--to=tony@atomide.com \
--cc=af@iseebcn.com \
--cc=devicetree@vger.kernel.org \
--cc=eballetbo@iseebcn.com \
--cc=egavin@iseebcn.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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).