From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932688AbaLBBBq (ORCPT ); Mon, 1 Dec 2014 20:01:46 -0500 Received: from mail-pd0-f173.google.com ([209.85.192.173]:55198 "EHLO mail-pd0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754193AbaLBBBo (ORCPT ); Mon, 1 Dec 2014 20:01:44 -0500 From: Kevin Hilman To: "Rafael J. Wysocki" Cc: Linux PM list , Linux PCI , Linux Kernel Mailing List , ACPI Devel Maling List , Alan Stern , Bjorn Helgaas , Ulf Hansson , Geert Uytterhoeven Subject: Re: [PATCH 0/4] PM: Use CONFIG_PM instead of CONFIG_PM_RUNTIME in core code References: <37310416.jZXoh5nfSC@vostro.rjw.lan> Date: Mon, 01 Dec 2014 17:01:40 -0800 In-Reply-To: <37310416.jZXoh5nfSC@vostro.rjw.lan> (Rafael J. Wysocki's message of "Thu, 27 Nov 2014 01:37:13 +0100") Message-ID: <7hd28250gb.fsf@deeprootsystems.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org "Rafael J. Wysocki" writes: > Hi, > > After commit b2b49ccbdd54 "PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is > selected" (currently in Linux next) CONFIG_PM_RUNTIME is set whenever > CONFIG_PM is set, so CONFIG_PM can be used in #ifdefs instead of > CONFIG_PM_RUNTIME which simplifies things in quite a few cases. > > For this reason, the following patches modify some core code to use > CONFIG_PM instead of CONFIG_PM_RUNTIME. > > [1/4] Drop a macro which is redundant after the above commit. > [2/4] Use PM instead of PM_RUNTIME in the core device PM code. > [3/4] Use PM instead of PM_RUNTIME in the ACPI core. > [4/4] Use PM instead of PM_RUNTIME in the PCI core. > > They build for me for all of the relevant combinations of options (on x86), > but more testing (on the other architectures) would be welcome. Acked-by: Kevin Hilman I gave this a quick boot test on all the OMAP boards I have, and it's booting fine. As soon as this hits linux-next, it will be boot tested on a pile of different ARM platforms, and will let you know what happens. Kevin