From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keerthy Subject: Re: [PATCH 0/3] ARM: dts: AM43x: Fix DCDC3 regulator voltage Date: Fri, 7 Nov 2014 11:00:46 +0530 Message-ID: <545C5906.6080204@ti.com> References: <1415271004-10935-1-git-send-email-j-keerthy@ti.com> <20141106182526.GC31454@atomide.com> <545C580F.30606@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from comal.ext.ti.com ([198.47.26.152]:33585 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751373AbaKGFdq (ORCPT ); Fri, 7 Nov 2014 00:33:46 -0500 In-Reply-To: <545C580F.30606@ti.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Robert Nelson Cc: Tony Lindgren , Keerthy , "linux-omap@vger.kernel.org" , devicetree , galak@codeaurora.org, mark.rutland@arm.com, pawel.moll@arm.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 wrote: >>> * Keerthy [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, >> >