Linux Power Management development
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jisheng Zhang <jszhang@marvell.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Steve Longerbeam <slongerbeam@gmail.com>,
	Eugeniu Rosca <erosca@de.adit-jv.com>,
	Joshua Frkuska <joshua_frkuska@mentor.com>,
	Eugeniu Rosca <roscaeugeniu@gmail.com>
Subject: Re: [PATCH v2] drivers: base: add support to skip power management in device/driver model
Date: Thu, 14 Feb 2019 12:05:09 +0000	[thread overview]
Message-ID: <20190214120509.GA28292@e107155-lin> (raw)
In-Reply-To: <20190214111609.GC28361@e107155-lin>

On Thu, Feb 14, 2019 at 11:16:09AM +0000, Sudeep Holla wrote:
> On Wed, Feb 13, 2019 at 11:17:47PM +0100, Rafael J. Wysocki wrote:
> > On Wed, Feb 13, 2019 at 1:01 PM Sudeep Holla <sudeep.holla@arm.com> wrote:

[...]

> > > diff --git a/drivers/base/power/main.c b/drivers/base/power/main.c
> > > index 0992e67e862b..2a29c3d4e240 100644
> > > --- a/drivers/base/power/main.c
> > > +++ b/drivers/base/power/main.c
> > > @@ -124,6 +124,10 @@ void device_pm_unlock(void)
> > >   */
> > >  void device_pm_add(struct device *dev)
> > >  {
> > > +       /* No need to create pm sysfs if explicitly specified as not required */
> >
> > Is this really about sysfs?
> >
>
> Nope, copy-paste from dpm_sysfs_add, will drop it.
>
> > > +       if (device_pm_not_required(dev))
> >
> > Should power.disable_depth be bumped up here or while setting the "no PM" flag?
> >
>
> OK, I missed that.
>

Looking at it,
1. We can't set it when we set "no PM" flag as pm_runtime_init called later
   initialise it to 1
2. We can bump it here, but I see it's usage self contained in runtime.c
   and may look odd to access it here.

More basic question is should we really need to bump it to 2 as its
initialised to 1 in runtime_init.

--
Regards,
Sudeep

  reply	other threads:[~2019-02-14 12:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13 12:01 [PATCH v2] drivers: base: add support to skip power management in device/driver model Sudeep Holla
2019-02-13 20:03 ` Ulf Hansson
2019-02-13 22:17 ` Rafael J. Wysocki
2019-02-14 11:16   ` Sudeep Holla
2019-02-14 12:05     ` Sudeep Holla [this message]
2019-02-14 17:34       ` Rafael J. Wysocki
2019-02-13 22:38 ` Eugeniu Rosca
2019-02-14 10:29   ` Sudeep Holla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190214120509.GA28292@e107155-lin \
    --to=sudeep.holla@arm.com \
    --cc=erosca@de.adit-jv.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joshua_frkuska@mentor.com \
    --cc=jszhang@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=roscaeugeniu@gmail.com \
    --cc=slongerbeam@gmail.com \
    --cc=ulf.hansson@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox