From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tero Kristo Subject: Re: [REPOST PATCH 0/2] ARM: OMAP3+: VCVP mapping fixes to get DVFS working Date: Fri, 17 Oct 2014 08:55:31 +0300 Message-ID: <5440AF53.9090003@ti.com> References: <1412949989-20186-1-git-send-email-t-kristo@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from bear.ext.ti.com ([192.94.94.41]:42971 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753325AbaJQF4C (ORCPT ); Fri, 17 Oct 2014 01:56:02 -0400 In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Enric Balletbo Serra Cc: linux-omap@vger.kernel.org, broonie@kernel.org, lgirdwood@gmail.com, nm@ti.com, Tony Lindgren , linux-arm-kernel@lists.infradead.org On 10/16/2014 05:21 PM, Enric Balletbo Serra wrote: > Hi, > > 2014-10-10 16:06 GMT+02:00 Tero Kristo : >> Hi, >> >> Seems like MPU DVFS does not scale the voltages currently with DT boot, >> due to missing mapping between regulator -> VCVP. Fixed this by adding >> support for platform data in the TWL regulator DT case + adding platform >> data quirk for the same. This same already works in the legacy boot, the >> platform data is passed fine. >> >> Tested on omap3-beagle by measuring the MPU voltage rail. >> >> OMAP4+ platforms do not currently register DVFS regulator, so this set by >> itself does not fix OMAP4 (needs the TPS MPU regulator added to DT etc. >> for OMAP4460.) >> >> -Tero >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-omap" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > Tony proposed in the IRC apply this patch series in order to solve the > following error messages with kernel 3.17 > > [ 2.522949] omap2_set_init_voltage: unable to find boot up OPP for > vdd_mpu_iva > [ 2.533721] omap2_set_init_voltage: unable to set vdd_mpu_iva > [ 2.541564] omap2_set_init_voltage: unable to find boot up OPP for vdd_core > [ 2.551208] omap2_set_init_voltage: unable to set vdd_core > > I'm using omap3-igep0020, I didn't mesure the MPU voltage rail but > should these patches solve these errors ? Did you resolve these errors > on your Beagleboard ? These prints are caused by something else: namely the fact that beagleboard rev C4+ boots up at 720MHz. This OPP is not supported by the kernel and quelches out the warning prints. This should be fixed by modifying the OPP tables under the dtsi files, however the nasty thing is not all beagleboards support 720MHz OPP. You either need to specify a dts file for beagle-revC4 or do some kernel magic to manually disable the 720MHz OPP on non-supported boards. -Tero From mboxrd@z Thu Jan 1 00:00:00 1970 From: t-kristo@ti.com (Tero Kristo) Date: Fri, 17 Oct 2014 08:55:31 +0300 Subject: [REPOST PATCH 0/2] ARM: OMAP3+: VCVP mapping fixes to get DVFS working In-Reply-To: References: <1412949989-20186-1-git-send-email-t-kristo@ti.com> Message-ID: <5440AF53.9090003@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 10/16/2014 05:21 PM, Enric Balletbo Serra wrote: > Hi, > > 2014-10-10 16:06 GMT+02:00 Tero Kristo : >> Hi, >> >> Seems like MPU DVFS does not scale the voltages currently with DT boot, >> due to missing mapping between regulator -> VCVP. Fixed this by adding >> support for platform data in the TWL regulator DT case + adding platform >> data quirk for the same. This same already works in the legacy boot, the >> platform data is passed fine. >> >> Tested on omap3-beagle by measuring the MPU voltage rail. >> >> OMAP4+ platforms do not currently register DVFS regulator, so this set by >> itself does not fix OMAP4 (needs the TPS MPU regulator added to DT etc. >> for OMAP4460.) >> >> -Tero >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-omap" in >> the body of a message to majordomo at vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > Tony proposed in the IRC apply this patch series in order to solve the > following error messages with kernel 3.17 > > [ 2.522949] omap2_set_init_voltage: unable to find boot up OPP for > vdd_mpu_iva > [ 2.533721] omap2_set_init_voltage: unable to set vdd_mpu_iva > [ 2.541564] omap2_set_init_voltage: unable to find boot up OPP for vdd_core > [ 2.551208] omap2_set_init_voltage: unable to set vdd_core > > I'm using omap3-igep0020, I didn't mesure the MPU voltage rail but > should these patches solve these errors ? Did you resolve these errors > on your Beagleboard ? These prints are caused by something else: namely the fact that beagleboard rev C4+ boots up at 720MHz. This OPP is not supported by the kernel and quelches out the warning prints. This should be fixed by modifying the OPP tables under the dtsi files, however the nasty thing is not all beagleboards support 720MHz OPP. You either need to specify a dts file for beagle-revC4 or do some kernel magic to manually disable the 720MHz OPP on non-supported boards. -Tero