From: Keerthy <a0393675@ti.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>, Keerthy <j-keerthy@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
galak@codeaurora.org, mark.rutland@arm.com, pawel.moll@arm.com
Subject: Re: [PATCH 0/3] ARM: dts: AM43x: Fix DCDC3 regulator voltage
Date: Fri, 7 Nov 2014 11:00:46 +0530 [thread overview]
Message-ID: <545C5906.6080204@ti.com> (raw)
In-Reply-To: <545C580F.30606@ti.com>
On Friday 07 November 2014 10:56 AM, Keerthy wrote:
> On Friday 07 November 2014 12:59 AM, Robert Nelson wrote:
>> On Thu, Nov 6, 2014 at 12:25 PM, Tony Lindgren <tony@atomide.com> wrote:
>>> * Keerthy <j-keerthy@ti.com> [141106 02:55]:
>>>> Fix DCDC3 volatge to 1.5V which is the right value to be supplied by
>>>> DCDC3 for all the boards.
>>> Hmm so what about the comments for similar beaglebone changes
>>> in thread "[PATCH] ARM: dts: am335x-boneblack: set dcdc1 regulator
>>> for 1.35v ddr3"?
>> Based on Keerthy's patchset, i think we should just ignore my "1.35v"
>> ddr3 patch for the beaglebone black. As by default it will be at
>> 1.50v. (so we can either define it for clarity at 1.50v or just ignore
>> it.)
>>
>> Keerthy,
>>
>> Are you guys seeing these same ddr lockups if u-boot correctly set's
>> the 1.35v level first? Or should we just really leave it at the
>> default power on voltage level? (till either u-boot or kernel grows
>> the capabilities to correctly tell the ddr3 we are changing it's
>> voltage.)
>
> Robert,
>
> In our case even u-boot lets it to be at 1.5V. The problem is
> when the regulators are registered we try to set it 1.35V since
> that is what we are passing from device tree. I see lock up
> on the latest boards we have.
The issue is seen when we are executing from DDR and the voltage is changed
(in our case lowered) on the fly.
>
> Regards,
> Keerthy
>
>
>>
>> Regards,
>>
>
next prev parent reply other threads:[~2014-11-07 5:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 10:50 [PATCH 0/3] ARM: dts: AM43x: Fix DCDC3 regulator voltage Keerthy
2014-11-06 10:50 ` [PATCH 1/3] ARM: dts: AM43x-EPOS-EVM: Fix DCDC3 voltage Keerthy
2014-11-06 10:50 ` [PATCH 2/3] ARM: dts: AM437x-GP-EVM: " Keerthy
2014-11-06 10:50 ` [PATCH 3/3] ARM: dts: AM437x-SK-EVM: " Keerthy
2014-11-06 13:45 ` [PATCH 0/3] ARM: dts: AM43x: Fix DCDC3 regulator voltage Nishanth Menon
2014-11-06 18:25 ` Tony Lindgren
2014-11-06 19:29 ` Robert Nelson
2014-11-07 5:26 ` Keerthy
2014-11-07 5:30 ` Keerthy [this message]
2014-11-10 17:05 ` Tony Lindgren
[not found] ` <20141106182526.GC31454-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2014-11-07 4:46 ` Keerthy
2014-11-07 8:38 ` Keerthy
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=545C5906.6080204@ti.com \
--to=a0393675@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=j-keerthy@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robertcnelson@gmail.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;
as well as URLs for NNTP newsgroup(s).