All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@kernel.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	linux-pm@vger.kernel.org, Len Brown <len.brown@intel.com>,
	Pavel Machek <pavel@ucw.cz>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Eduardo Valentin <edubezval@gmail.com>
Subject: Re: [PATCH v2] Driver core: Re-init runtime PM states at probe error and driver unbind
Date: Wed, 18 Nov 2015 10:27:15 -0800	[thread overview]
Message-ID: <7hoaerxiws.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1447843719-9501-1-git-send-email-ulf.hansson@linaro.org> (Ulf Hansson's message of "Wed, 18 Nov 2015 11:48:39 +0100")

Ulf Hansson <ulf.hansson@linaro.org> writes:

> There are two common expectations among several subsystems/drivers that
> deploys runtime PM support, but which isn't met by the driver core.

[...]

> To address these issues, let's change the policy of the driver core to
> meet these expectations. More precisely, at ->probe() failures and driver
> unbind, restore the initial states of runtime PM.
>
> Although to still allow subsystem's to control PM for devices that doesn't
> ->probe() successfully, don't restore the initial states unless runtime PM
> is disabled.
>
> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>

Reviewed-by: Kevin Hilman <khilman@linaro.org>

Thanks for the detailed changelog!

Kevin

  reply	other threads:[~2015-11-18 18:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 10:48 [PATCH v2] Driver core: Re-init runtime PM states at probe error and driver unbind Ulf Hansson
2015-11-18 18:27 ` Kevin Hilman [this message]
2015-12-02  2:16   ` Rafael J. Wysocki

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=7hoaerxiws.fsf@deeprootsystems.com \
    --to=khilman@kernel.org \
    --cc=edubezval@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=len.brown@intel.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    --cc=stern@rowland.harvard.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.