From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: OMAP 4430 SDP: rather sick with recent kernels Date: Wed, 17 Dec 2014 09:34:47 -0800 Message-ID: <20141217173446.GG2950@atomide.com> References: <20141217095252.GH11502@n2100.arm.linux.org.uk> <20141217172333.GE23854@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:64731 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750954AbaLQRhn (ORCPT ); Wed, 17 Dec 2014 12:37:43 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Nishanth Menon Cc: Russell King - ARM Linux , linux-omap , "linux-arm-kernel@lists.infradead.org" , Tero Kristo , Tomi Valkeinen , Joel Fernandes , Peter Ujfalusi , Jyri Sarha * Nishanth Menon [141217 09:35]: > On Wed, Dec 17, 2014 at 11:23 AM, Tony Lindgren wrote: > > > >> twl: not initialized > >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1410000 Vs max 1316660 > > > > This seems to be some twl related init order issue, I'll take a > > look at this one. > > > >> omap2_set_init_voltage: unable to find boot up OPP for vdd_mpu > >> omap2_set_init_voltage: unable to set vdd_mpu > >> omap2_set_init_voltage: unable to find boot up OPP for vdd_core > >> omap2_set_init_voltage: unable to set vdd_core > >> omap2_set_init_voltage: unable to find boot up OPP for vdd_iva > >> omap2_set_init_voltage: unable to set vdd_iva > > > > I believe Nishanth has some plans for these? > > > Not in the near future. looks like converting VC/VP into regulator and > fit inside DT world has gone no where.. Looks like also the "twl: not initialized" error is caused by this: omap2_common_pm_late_init omap_voltage_late_init omap_vc_init_channel omap_vc_calc_vsel twl6030_uv_to_vsel twl_i2c_read twl_get_regmap Can't we fix it with pdata-quirks.c as this error is now showing up on at least omap3 and 4? Regards, Tony From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Wed, 17 Dec 2014 09:34:47 -0800 Subject: OMAP 4430 SDP: rather sick with recent kernels In-Reply-To: References: <20141217095252.GH11502@n2100.arm.linux.org.uk> <20141217172333.GE23854@atomide.com> Message-ID: <20141217173446.GG2950@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Nishanth Menon [141217 09:35]: > On Wed, Dec 17, 2014 at 11:23 AM, Tony Lindgren wrote: > > > >> twl: not initialized > >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > >> twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1410000 Vs max 1316660 > > > > This seems to be some twl related init order issue, I'll take a > > look at this one. > > > >> omap2_set_init_voltage: unable to find boot up OPP for vdd_mpu > >> omap2_set_init_voltage: unable to set vdd_mpu > >> omap2_set_init_voltage: unable to find boot up OPP for vdd_core > >> omap2_set_init_voltage: unable to set vdd_core > >> omap2_set_init_voltage: unable to find boot up OPP for vdd_iva > >> omap2_set_init_voltage: unable to set vdd_iva > > > > I believe Nishanth has some plans for these? > > > Not in the near future. looks like converting VC/VP into regulator and > fit inside DT world has gone no where.. Looks like also the "twl: not initialized" error is caused by this: omap2_common_pm_late_init omap_voltage_late_init omap_vc_init_channel omap_vc_calc_vsel twl6030_uv_to_vsel twl_i2c_read twl_get_regmap Can't we fix it with pdata-quirks.c as this error is now showing up on at least omap3 and 4? Regards, Tony