public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Tony Lindgren <tony@atomide.com>, Eduard Gavin <egavin@iseebcn.com>
Cc: "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 14:19:15 -0500	[thread overview]
Message-ID: <5734D733.9060400@ti.com> (raw)
In-Reply-To: <20160512165755.GR5995@atomide.com>

On 05/12/2016 11:57 AM, Tony Lindgren wrote:
> * Eduard Gavin <egavin@iseebcn.com> [160509 07:43]:
>> Dear Nishanth,
>>   In igepV5 the LDO7 is connected to:
>>     VDDA_DSIPORTA - ball AA33
>>     VDDA_DSIPORTC - ball AE33
>>     VDDA_HDMI - ball AN25
>>   LDO4 is connected to:
>>     VPP1 - ball AD9
> 
> Thanks for the info, here's an updated patch with comments and now
> using 1.8V instead of the 2.0V omap5-board-common.dtsi.
> 
> Regards,
> 
> Tony
> 
> 8< -----------------
> From: Tony Lindgren <tony@atomide.com>
> Date: Mon, 9 May 2016 07:51:00 -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,16 @@
>  	};
>  };
>  
> +/*
> + * 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.

> + */
> +&ldo7_reg {
> +	status = "okay";
> +	regulator-min-microvolt = <1800000>;
> +	regulator-max-microvolt = <1800000>;
> +};
> +
>  &omap5_pmx_core {
>  	i2c4_pins: pinmux_i2c4_pins {
>  		pinctrl-single,pins = <
> 


-- 
Regards,
Nishanth Menon

  reply	other threads:[~2016-05-12 19:19 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
     [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 [this message]
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=5734D733.9060400@ti.com \
    --to=nm@ti.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=tony@atomide.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