From: vaibhav.hiremath@linaro.org (Vaibhav Hiremath)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] clk: 88pm800: Add clk provider driver for 88pm800 family of devices
Date: Wed, 22 Jul 2015 13:46:53 +0530 [thread overview]
Message-ID: <55AF5175.2010701@linaro.org> (raw)
In-Reply-To: <55AF3C2E.7010205@samsung.com>
On Wednesday 22 July 2015 12:16 PM, Krzysztof Kozlowski wrote:
> On 22.07.2015 15:27, Vaibhav Hiremath wrote:
>>
>>
>> On Wednesday 22 July 2015 02:22 AM, Stephen Boyd wrote:
>>> On 07/21/2015 12:36 PM, Vaibhav Hiremath wrote:
>>>>
>>>> On Wednesday 22 July 2015 12:40 AM, Stephen Boyd wrote:
>>>>> On 07/21/2015 04:07 AM, Vaibhav Hiremath wrote:
>>>>>> +
>>
>> <snip>
>>
>>>>>> +static int pm800_clk_remove(struct platform_device *pdev)
>>>>>> +{
>>>>>> + struct pm800_clk *pm800_clks = platform_get_drvdata(pdev);
>>>>>> + int i;
>>>>>> +
>>>>>> + of_clk_del_provider(pm800_clks[0].clk_np);
>>>>>> + /* Drop the reference obtained in pm800_clk_parse_dt */
>>>>>> + of_node_put(pm800_clks[0].clk_np);
>>>>>
>>>>> This is odd. Why are we keeping the reference in the driver?
>>>>>
>>>>
>>>> Honestly I do not have any good answer here. I have to admit that it is
>>>> getting carry forwarded from legacy driver.
>>>>
>>>
>>> Well we shouldn't do things if we don't know why we're doing them.
>>> Krzysztof?
>
> I am really busy now so I am not following closely other discussions. I
> assume you are referring to clk-s2mps11.c. The of_node_put() matches
> of_get_child_by_name() when parsing DT.
>
> So why not of_node_put() just after parsing DT? Well, the result of
> of_get_child_by_name() is stored in state container for entire device
> life-cycle so we can use it in of_clk_del_provider().
>
> That was the idea behind it. If it looks incorrect I would be happy to
> see a patch :) .
>
About to respond, I digged more on kobject stuff and sequence in
of/dynamic.c and
I think you are right, we need of_node_put, as a result of
of_get_child_by_name().
Stephen,
Please let me know if you think otherwise.
Thanks,
Vaibhav
next prev parent reply other threads:[~2015-07-22 8:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 11:06 [PATCH 0/4] clk: 88pm800: Add new clk provider driver for 88PM800 MFD Vaibhav Hiremath
2015-07-21 11:07 ` [PATCH 1/4] mfd: 88pm800: Update the header file with 32K clk related macros Vaibhav Hiremath
2015-07-23 15:52 ` Lee Jones
2015-08-05 8:53 ` Vaibhav Hiremath
2015-07-21 11:07 ` [PATCH 2/4] mfd: devicetree: bindings: Add clock subdevice node information Vaibhav Hiremath
2015-07-23 5:08 ` Krzysztof Kozlowski
2015-07-30 22:13 ` Stephen Boyd
2015-07-30 22:21 ` Rob Herring
2015-08-05 6:39 ` Vaibhav Hiremath
2015-07-21 11:07 ` [PATCH 3/4] clk: 88pm800: Add clk provider driver for 88pm800 family of devices Vaibhav Hiremath
2015-07-21 19:10 ` Stephen Boyd
2015-07-21 19:36 ` Vaibhav Hiremath
2015-07-21 20:52 ` Stephen Boyd
2015-07-22 6:27 ` Vaibhav Hiremath
2015-07-22 6:46 ` Krzysztof Kozlowski
2015-07-22 8:16 ` Vaibhav Hiremath [this message]
2015-07-22 22:03 ` Stephen Boyd
2015-07-21 11:07 ` [PATCH 4/4] mfd: 88pm800: Add support for clk subdevice Vaibhav Hiremath
2015-07-23 4:58 ` Krzysztof Kozlowski
2015-07-23 15:50 ` Lee Jones
2015-08-05 9:07 ` Vaibhav Hiremath
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=55AF5175.2010701@linaro.org \
--to=vaibhav.hiremath@linaro.org \
--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).