From: jonathanh@nvidia.com (Jon Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 6/8] PM / Domains: Remove a provider by referencing the data pointer
Date: Thu, 11 Aug 2016 17:39:54 +0100 [thread overview]
Message-ID: <18ad702c-83fe-fd6d-89ae-57e6f2715860@nvidia.com> (raw)
In-Reply-To: <CAPDyKFovC07Z9y-4RQ4MKGtjJx5w1D8er3Fv-8HF2qyTKgVViQ@mail.gmail.com>
On 05/08/16 12:55, Ulf Hansson wrote:
> On 21 June 2016 at 15:47, Jon Hunter <jonathanh@nvidia.com> wrote:
>>
>> On 15/06/16 15:38, Ulf Hansson wrote:
>>> On 4 March 2016 at 12:23, Jon Hunter <jonathanh@nvidia.com> wrote:
>>>> To remove a PM domain from the system, it is necessary to ensure
>>>> that any PM domain providers associated with the PM domain have
>>>> been removed. Otherwise it could be possible to obtain a pointer
>>>> to a PM domain structure that has been removed.
>>>>
>>>> PM domains now have a reference to the pointer for the PM domain
>>>> provider's data variable. Add a function so that a PM domain can
>>>> remove a PM domain provider by referencing the data pointer.
>
>
>>>>
>>>> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
>>>> ---
>>>> drivers/base/power/domain.c | 24 ++++++++++++++++++++++++
>>>> include/linux/pm_domain.h | 2 ++
>>>> 2 files changed, 26 insertions(+)
>>>>
>>>> diff --git a/drivers/base/power/domain.c b/drivers/base/power/domain.c
>>>> index 72055fef6256..438885f2455f 100644
>>>> --- a/drivers/base/power/domain.c
>>>> +++ b/drivers/base/power/domain.c
>>>> @@ -1738,6 +1738,30 @@ void of_genpd_del_provider(struct device_node *np)
>>>> EXPORT_SYMBOL_GPL(of_genpd_del_provider);
>>>>
>>>> /**
>>>> + * of_genpd_del_provider_by_data() - Remove a registered PM domain provider
>>>> + * @data: Pointer to the data associated with the PM domain provider
>>>> + *
>>>> + * Look up a PM domain provider based upon a pointer to it's data and
>>>> + * remove the PM domain provider from the list of providers.
>>>> + */
>>>> +void of_genpd_del_provider_by_data(void *data)
>>>> +{
>>>> + struct of_genpd_provider *c, *cp;
>>>> +
>>>> + mutex_lock(&of_genpd_mutex);
>>>> + list_for_each_entry_safe(cp, c, &of_genpd_providers, link) {
>>>> + if (cp->data == data) {
>>>> + list_del(&cp->link);
>>>> + of_node_put(cp->node);
>>>> + kfree(cp);
>>>> + break;
>>>> + }
>>>> + }
>>>> + mutex_unlock(&of_genpd_mutex);
>>>> +}
>>>> +EXPORT_SYMBOL_GPL(of_genpd_del_provider_by_data);
>>>> +
>>>> +/**
>>>> * of_genpd_get_from_provider() - Look-up PM domain
>>>> * @genpdspec: OF phandle args to use for look-up
>>>> *
>>>> diff --git a/include/linux/pm_domain.h b/include/linux/pm_domain.h
>>>> index bed84413546f..7b7921a65cb0 100644
>>>> --- a/include/linux/pm_domain.h
>>>> +++ b/include/linux/pm_domain.h
>>>> @@ -199,6 +199,7 @@ int of_genpd_add_provider_simple(struct device_node *np,
>>>> int of_genpd_add_provider_onecell(struct device_node *np,
>>>> struct genpd_onecell_data *data);
>>>> void of_genpd_del_provider(struct device_node *np);
>>>
>>> There's currently only one user of of_genpd_del_provider().
>>>
>>> Could this patch just convert that user to the new API, so we don't
>>> need to keep both the legacy and new one?
>>>
>>> I guess we could then just stick to the name "of_genpd_del_provider()".
>>
>> I had a look at this and to do that we would end up with
>> of_genpd_del_provider(struct device_node *np, void *data) where the user
>> should only pass one of the arguments. It seems a bit odd. However,
>> unless I have forgotten something, I wonder if we should just make
>> of_genpd_del_provider_by_name() a local function and not export this at
>> all? It seems more natural for users to delete a provider by the
>> device_node than by name rather than the data argument.
>>
>> The only problem I see with making of_genpd_del_provider_by_name() local
>> is that I need to add a prototype for the function at the top of the
>> domain.c source file so that it builds because __pm_genpd_remove() is
>> defined above it. Yes I could move __pm_genpd_remove() to the bottom of
>> the file but then it is not located next to pm_genpd_init() which seems odd.
>>
>> Let me know what you think.
>
> Sorry for delay! I have now looked into this in more detail.
No problem. Thanks!
> When an genpd provider is added today, it's supposed to get a
> corresponding *unique* OF device node associated with it, right!?
>
> If we store this OF device node from the provider in the struct
> generic_pm_domain, instead of the "provider_data pointer", we wouldn't
> need to the add of_genpd_del_provider_by_data() at all. Because we can
> use the currently available of_genpd_del_provider(), right!?
>
> Or what am I missing? :-)
No that would work as well. I guess I was trying to make it non-DT
specific. However, for now it can be to simplify matters and it could
always be extended later if necessary.
I am also thinking about making pm_genpd_remove_tail()
of_genpd_remove_tail() as it seems silly to have both a struct device
pointer and a struct device_node pointer stored for the provider.
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2016-08-11 16:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 11:23 [RFC PATCH 0/8] PM / Domains: Add support for removing PM domains Jon Hunter
2016-03-04 11:23 ` [RFC PATCH 1/8] PM / Domains: Add new helper functions for device-tree Jon Hunter
2016-06-22 11:00 ` Jon Hunter
2016-06-22 14:58 ` Jon Hunter
2016-06-22 15:08 ` Ulf Hansson
2016-06-22 15:22 ` Jon Hunter
2016-06-22 15:36 ` Ulf Hansson
2016-03-04 11:23 ` [RFC PATCH 2/8] ARM: EXYNOS: Remove calls to of_genpd_get_from_provider() Jon Hunter
2016-03-04 11:23 ` [RFC PATCH 3/8] staging: board: " Jon Hunter
2016-03-04 11:23 ` [RFC PATCH 4/8] PM / Domains: Don't expose generic_pm_domain structure Jon Hunter
2016-08-05 11:55 ` Ulf Hansson
2016-03-04 11:23 ` [RFC PATCH 5/8] PM / Domains: Verify the PM domain is present when adding a provider Jon Hunter
2016-08-05 11:57 ` Ulf Hansson
2016-03-04 11:23 ` [RFC PATCH 6/8] PM / Domains: Remove a provider by referencing the data pointer Jon Hunter
2016-06-15 14:38 ` Ulf Hansson
2016-06-21 13:47 ` Jon Hunter
2016-07-11 13:14 ` Jon Hunter
2016-08-05 11:55 ` Ulf Hansson
2016-08-11 16:39 ` Jon Hunter [this message]
2016-08-12 0:24 ` Rafael J. Wysocki
2016-06-21 14:45 ` Jon Hunter
2016-03-04 11:23 ` [RFC PATCH 7/8] PM / Domains: Prepare for adding support to remove PM domains Jon Hunter
2016-03-04 11:23 ` [RFC PATCH 8/8] PM / Domains: Add support for removing " Jon Hunter
2016-06-15 14:33 ` Ulf Hansson
2016-06-21 14:08 ` Jon Hunter
2016-03-04 12:33 ` [RFC PATCH 0/8] " Ulf Hansson
2016-03-28 12:38 ` Jon Hunter
2016-06-06 13:19 ` Jon Hunter
2016-06-15 14:46 ` Ulf Hansson
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=18ad702c-83fe-fd6d-89ae-57e6f2715860@nvidia.com \
--to=jonathanh@nvidia.com \
--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;
as well as URLs for NNTP newsgroup(s).