Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: rjw@rjwysocki.net (Rafael J. Wysocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 00/10] PM / Domains: Add support for removing PM domains
Date: Wed, 14 Sep 2016 02:58:34 +0200	[thread overview]
Message-ID: <14914984.irHbtjz3da@vostro.rjw.lan> (raw)
In-Reply-To: <1473678074-15126-1-git-send-email-jonathanh@nvidia.com>

On Monday, September 12, 2016 12:01:04 PM Jon Hunter wrote:
> In order to safely remove PM domains there are a few changes that need to be
> made to ensure that no one is holding an external reference to a PM domain
> after it has been removed. One solution, implemented here, solves this by
> eliminating external references to PM domain.
> 
> Changes from V1:
> - Added test when removing a PM domain to ensure the PM domain provider
>   has been removed.
> - Re-organised patches 8-10 so that patch #8 adds the code to verify if
>   the provider is present, patch #9 adds basic support for removing PM
>   domains and patch #10 adds support for removing PM domains by provider.
> 
> Changes from initial RFC:
> - Renamed functions made static per Ulf's feedback.
> - Added patch to clean-up provider/xlate APIs per Ulf's feedback
> - Re-worked and simplified the association between PM domains and PM
>   domain providers. Dropped the 'provider_data' variable from the
>   generic_pm_domain structure in favour of using the fwnode_handle.
> - Split patch for removing PM domains into multiple patches per Ulf's
>   feedback.
> 
> Jon Hunter (10):
>   PM / Domains: Add new helper functions for device-tree
>   ARM: EXYNOS: Remove calls to of_genpd_get_from_provider()
>   staging: board: Remove calls to of_genpd_get_from_provider()
>   PM / Domains: Don't expose generic_pm_domain structure to clients
>   PM / Domains: Don't expose xlate and provider helper functions
>   PM / Domains: Verify the PM domain is present when adding a provider
>   PM / Domains: Prepare for adding support to remove PM domains
>   PM / Domains: Store the provider in the PM domain structure
>   PM / Domains: Add support for removing PM domains
>   PM / Domains: Add support for removing nested PM domains by provider

All applied.

I'll expose a branch containing them after they've spent a couple of days in
linux-next.

Thanks,
Rafael

      parent reply	other threads:[~2016-09-14  0:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12 11:01 [PATCH V2 00/10] PM / Domains: Add support for removing PM domains Jon Hunter
2016-09-12 11:01 ` [PATCH V2 01/10] PM / Domains: Add new helper functions for device-tree Jon Hunter
2016-09-12 11:01 ` [PATCH V2 02/10] ARM: EXYNOS: Remove calls to of_genpd_get_from_provider() Jon Hunter
2016-09-12 11:01 ` [PATCH V2 03/10] staging: board: " Jon Hunter
2016-09-12 11:01 ` [PATCH V2 04/10] PM / Domains: Don't expose generic_pm_domain structure to clients Jon Hunter
2016-09-12 11:01 ` [PATCH V2 05/10] PM / Domains: Don't expose xlate and provider helper functions Jon Hunter
2016-09-12 11:01 ` [PATCH V2 06/10] PM / Domains: Verify the PM domain is present when adding a provider Jon Hunter
2016-09-12 11:01 ` [PATCH V2 07/10] PM / Domains: Prepare for adding support to remove PM domains Jon Hunter
2016-09-12 11:01 ` [PATCH V2 08/10] PM / Domains: Store the provider in the PM domain structure Jon Hunter
2016-09-12 12:56   ` Ulf Hansson
2016-09-12 11:01 ` [PATCH V2 09/10] PM / Domains: Add support for removing PM domains Jon Hunter
2016-09-12 12:56   ` Ulf Hansson
2016-09-12 11:01 ` [PATCH V2 10/10] PM / Domains: Add support for removing nested PM domains by provider Jon Hunter
2016-09-12 12:56   ` Ulf Hansson
2016-09-12 13:02 ` [PATCH V2 00/10] PM / Domains: Add support for removing PM domains Ulf Hansson
2016-09-12 13:45   ` Rafael J. Wysocki
2016-09-14  0:58 ` Rafael J. Wysocki [this message]

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=14914984.irHbtjz3da@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=linux-arm-kernel@lists.infradead.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