From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx6: Revert "mx6: soc: Disable VDDPU regulator"
Date: Thu, 16 Jan 2014 17:08:30 +0100 [thread overview]
Message-ID: <52D803FE.3060607@denx.de> (raw)
In-Reply-To: <CAOMZO5BgT+gMV2Ow5+ZqymNhEP77MyPg9Rav=h+mj1J7E-kEXQ@mail.gmail.com>
Hi Fabio,
On 16/01/2014 17:01, Fabio Estevam wrote:
> On Thu, Jan 16, 2014 at 1:50 PM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>
>>> It worked for you probably because you used the ldo bypass mode.
>>
>>
>> Yes; I did the bypass mode.
>
> We currently don't do LDO bypass mode in mainline U-boot. We do it in
> FSL U-boot.
>
> With LDO bypass, lower VDDARM and VDDSOC voltages can be supplied as
> per the mx6 datasheet.
>
> I just measured with the scope and the VDDARM/SOC voltages supplied by
> the 3.10 FSL kernel are below the minimum for the LDO enabled case. So
> setting LDO bypass in U-boot 'fixes' the issue.
>
> We can implement LDO bypass after 2014.01 is out, but for this release
> let's just revert the VDDPU disable patch.
>
> Do you agree?
>
+1
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2014-01-16 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 12:57 [U-Boot] [PATCH] mx6: Revert "mx6: soc: Disable VDDPU regulator" Fabio Estevam
2014-01-16 13:06 ` Stefano Babic
2014-01-16 13:21 ` Fabio Estevam
2014-01-16 15:33 ` Otavio Salvador
2014-01-16 15:42 ` Fabio Estevam
2014-01-16 15:43 ` Fabio Estevam
2014-01-16 15:50 ` Otavio Salvador
2014-01-16 16:01 ` Fabio Estevam
2014-01-16 16:06 ` Otavio Salvador
2014-01-16 16:08 ` Stefano Babic [this message]
2014-01-16 16:12 ` Pierre AUBERT
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=52D803FE.3060607@denx.de \
--to=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
/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).