mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Tony Lindgren <tony@atomide.com>, Nishanth Menon <nm@ti.com>,
	"Valkeinen, Tomi" <tomi.valkeinen@ti.com>
Cc: linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	"Enric Balletbo i Serra" <eballetbo@iseebcn.com>,
	"Agustí Fontquerni" <af@iseebcn.com>,
	"Eduard Gavin" <egavin@iseebcn.com>
Subject: Re: [PATCH] ARM: dts: omap5-igep0050: Correct hdmi regulator
Date: Mon, 9 May 2016 11:25:53 +0300	[thread overview]
Message-ID: <a6969765-d07d-6d0e-36df-b78b485d9644@ti.com> (raw)
In-Reply-To: <20160505184609.GB5995@atomide.com>

Adding Tomi,

On 05/05/16 21:46, Tony Lindgren wrote:
> * Nishanth Menon <nm@ti.com> [160504 11:03]:
>> On 05/04/2016 12:26 PM, Tony Lindgren wrote:
>>> Hi,
>>>
>>> Adding Nishanth to Cc.
>>>
>>> * Peter Ujfalusi <peter.ujfalusi@ti.com> [160429 05:15]:
>>>> ldo7_reg, obviously ;)
>>>>
>>>>> 	status = "okay";
>>>>> 	regulator-min-microvolt = <1800000>;
>>>>> 	regulator-max-microvolt = <1800000>;
>>>>> };
>>>
>>> It really seems to be ldo7, otherwise there's no HDMI output. I don't
>>> have the schematics either.
>>>
>>> But it seems we have at least two other regressions in Linux next that
>>> prevent me from testing this properly:
>>>
>>> 1. On igepv5, I get this for the MMC regulator
>>>
>>> ldo9: bypassed regulator has no supply!
>>> ldo9: failed to get the current voltage(-517)
>>> palmas-pmic 48070000.i2c:palmas@48:palmas_pmic: failed to register 48070000.i2c:palmar
> 
> The patch I posted fixes this. Then for the HDMI see below.
> I've kept it at 2V like we have in omap5-board-common.dtsi,
> I wonder if it really should be 1.8V though for ldo7 in this
> case?

AFAIK the VDDA for the HDMI needs to be 1.8V along with other VDDAs for DSS
(vdda_dsiporta, vdda_dsiportc and vdda_hdmi).

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.

Just to note: on omap5-uevm the ldo7 is connected to VPP1 of OMAP5 (eFuse
power supply), which does require 2V.


> Regards,
> 
> Tony
> 8< -----------------
> From: Tony Lindgren <tony@atomide.com>
> Date: Thu, 5 May 2016 11:29:23 -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>
> 
> diff --git a/arch/arm/boot/dts/omap5-igep0050.dts b/arch/arm/boot/dts/omap5-igep0050.dts
> index 46ecb1d..72ff6a4 100644
> --- a/arch/arm/boot/dts/omap5-igep0050.dts
> +++ b/arch/arm/boot/dts/omap5-igep0050.dts
> @@ -35,6 +35,12 @@
>  	};
>  };
>  
> +&ldo7_reg {
> +	status = "okay";
> +	regulator-min-microvolt = <2000000>;
> +	regulator-max-microvolt = <2000000>;

If we are not changing the default voltage set in the common dtsi file we only
need to status = "okay"

> +};
> +
>  &omap5_pmx_core {
>  	i2c4_pins: pinmux_i2c4_pins {
>  		pinctrl-single,pins = <
> 


-- 
Péter

  reply	other threads:[~2016-05-09  8:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29 10:21 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 [this message]
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

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=a6969765-d07d-6d0e-36df-b78b485d9644@ti.com \
    --to=peter.ujfalusi@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=nm@ti.com \
    --cc=tomi.valkeinen@ti.com \
    --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

all inboxes | Powered by JetHome®