From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934026AbcAYSQH (ORCPT ); Mon, 25 Jan 2016 13:16:07 -0500 Received: from mail-pa0-f41.google.com ([209.85.220.41]:35589 "EHLO mail-pa0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933001AbcAYSQE convert rfc822-to-8bit (ORCPT ); Mon, 25 Jan 2016 13:16:04 -0500 From: Kevin Hilman To: Tony Lindgren Cc: Pali =?utf-8?Q?Roh=C3=A1r?= , Sebastian Reichel , Ivaylo Dimitrov , Pavel Machek , Aaro Koskinen , Nishanth Menon , linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Missing OMAP PM layer Organization: BayLibre References: <201601242123.58871@pali> <20160125163442.GU19432@atomide.com> Date: Mon, 25 Jan 2016 10:16:01 -0800 In-Reply-To: <20160125163442.GU19432@atomide.com> (Tony Lindgren's message of "Mon, 25 Jan 2016 08:34:42 -0800") Message-ID: <7hpowpr0da.fsf@baylibre.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Tony Lindgren writes: > * Pali Rohár [160124 12:24]: >> Hello, >> >> make menuconfig allows me to choose "OMAP PM layer selection" and the >> only one option is CONFIG_OMAP_PM_NOOP "No-op/debug PM layer". >> >> What does it mean? Power manager is noop? >> >> I see that it has only two corresponding files in mainline kernel: >> arch/arm/mach-omap2/omap-pm.h >> arch/arm/mach-omap2/omap-pm-noop.c >> >> Nokia's kernels (for N900 and N950) had also: >> arch/arm/mach-omap2/omap-pm-srf.c >> >> Can somebody explain it what happened with omap power management? >> >> Looks like that omap-pm.h provides some API, but the only implementation >> is noop which do nothing. > > I believe none of that is needed any longer in mainline. > > Kevin, care to descrbibe what should be done here? We had created the OMAP PM layer as a pluggable layer where we could experiment with different approaches for adding constratints, etc. I can't remember anymore what all was in there, but we gutted most of it after switching to runtime PM. The SRF was a "shared resource framework" that came out of a TI kernel that was never accepted upstream either, but was one of the implementation of the OMAP PM layer. Kevin