From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751980AbdFLHjw (ORCPT ); Mon, 12 Jun 2017 03:39:52 -0400 Received: from muru.com ([72.249.23.125]:51378 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751764AbdFLHjv (ORCPT ); Mon, 12 Jun 2017 03:39:51 -0400 Date: Mon, 12 Jun 2017 00:39:47 -0700 From: Tony Lindgren To: Sebastian Reichel Cc: Kevin Hilman , Russell King , linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] ARM: OMAP: PM: stop early on systems without twl Message-ID: <20170612073946.GU3730@atomide.com> References: <20170609223223.19079-1-sre@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170609223223.19079-1-sre@kernel.org> User-Agent: Mutt/1.8.2 (2017-04-18) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Sebastian Reichel [170609 15:36]: > Motorola Droid 4 has an OMAP4, but no TWL6030. It currently > complains verbosely about this during boot: > > 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 > 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 > > While proper support for CPCAP should be added at some point, > let's exit early in omap2_common_pm_late_init() until that > has been implemented to avoid the above errors. There is still > a reminder about missing PM in dmesg: > > Missing OMAP4 PM for this platform! Great good to see this dmesg spam go away. Applying into omap-for-v4.13/soc-v3 thanks. Tony