Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S942885AbcJSReq (ORCPT ); Wed, 19 Oct 2016 13:34:46 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:53648 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S936411AbcJSReo (ORCPT ); Wed, 19 Oct 2016 13:34:44 -0400 Date: Wed, 19 Oct 2016 13:34:42 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Anand Moon cc: Krzysztof Kozlowski , Greg Kroah-Hartman , Kukjin Kim , Javier Martinez Canillas , Linux USB Mailing List , linux-arm-kernel , "linux-samsung-soc@vger.kernel.org" , Linux Kernel Subject: Re: [PATCH 1/2] host: ehci-exynos: Convert to use the SET_SYSTEM_SLEEP_PM_OPS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1337 Lines: 49 On Wed, 19 Oct 2016, Anand Moon wrote: > I might be wrong, below is the kconfig option for PM_SLEEP > > Symbol: PM_SLEEP [=y] > Type : boolean > Defined at kernel/power/Kconfig > Depends on: SUSPEND [=y] || HIBERNATE_CALLBACKS [=n] > Selects: PM [=y] > > So we cannot set CONFIG_PM_SLEEP=n and CONFIG_PM=y You have it backward. We cannot set CONFIG_PM_SLEEP=y and CONFIG_PM=n. But you can have CONFIG_PM_SLEEP=n and CONFIG_PM=y. Alan Stern > I observed at many places were either CONFIG_PM or CONFIG_PM_SLEEP are used. > > So I would like to use SIMPLE_DEV_PM_OPS macro to set struct > dev_pm_ops exynos_ohci_pm_ops to correct the code. > > Best Regards > -Anand Moon > > > > >> > >> CONFIG_PM_SLEEP=n or > >> # CONFIG_PM_SLEEP is not set > >> > >> > 2. What will be the output with !SUSPEND && !HIBERNATE && PM? > >> > >> # > >> # Power management options > >> # > >> # CONFIG_SUSPEND is not set > >> # CONFIG_HIBERNATION is not set > >> # CONFIG_PM is not set > >> > >> When CONFIG_SUSPEND and CONFIG_HIBERNATION are not set > >> CONFIG_PM is disabled and so is CONFIG_PM_SLEEP. > > > > In my config, the CONFIG_PM was enabled thus the code changes the > > functionality... Maybe this was intented but I really don't get it from > > the commit message or from your explanations here. > > > > Krzysztof > >