From: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-arm-kernel@lists.infradead.org, robh+dt@kernel.org,
mturquette@baylibre.com, lee.jones@linaro.org,
k.kozlowski@samsung.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH 3/4] clk: 88pm800: Add clk provider driver for 88pm800 family of devices
Date: Wed, 22 Jul 2015 11:57:37 +0530 [thread overview]
Message-ID: <55AF37D9.3000006@linaro.org> (raw)
In-Reply-To: <55AEB103.9010205@codeaurora.org>
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?
>
Hold on,
After looking more in to this, it seems we really do not need it.
It is already taken care by
of_clk_add_provider() and
of_clk_del_provider()
Sorry for not investigating this before. Just left out from my eyes
somehow.
Actually I can cleanup clk-s2mps11.c driver as well, but only thing is
I can validate it, as I do not have platform to test it.
It should be trivial changes.
If somebody can help me out in validation I can submit the patch for
clk-s2mps11.c driver as well.
Thanks,
Vaibhav
WARNING: multiple messages have this Message-ID (diff)
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 11:57:37 +0530 [thread overview]
Message-ID: <55AF37D9.3000006@linaro.org> (raw)
In-Reply-To: <55AEB103.9010205@codeaurora.org>
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?
>
Hold on,
After looking more in to this, it seems we really do not need it.
It is already taken care by
of_clk_add_provider() and
of_clk_del_provider()
Sorry for not investigating this before. Just left out from my eyes
somehow.
Actually I can cleanup clk-s2mps11.c driver as well, but only thing is
I can validate it, as I do not have platform to test it.
It should be trivial changes.
If somebody can help me out in validation I can submit the patch for
clk-s2mps11.c driver as well.
Thanks,
Vaibhav
WARNING: multiple messages have this Message-ID (diff)
From: Vaibhav Hiremath <vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org,
lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
k.kozlowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 3/4] clk: 88pm800: Add clk provider driver for 88pm800 family of devices
Date: Wed, 22 Jul 2015 11:57:37 +0530 [thread overview]
Message-ID: <55AF37D9.3000006@linaro.org> (raw)
In-Reply-To: <55AEB103.9010205-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
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?
>
Hold on,
After looking more in to this, it seems we really do not need it.
It is already taken care by
of_clk_add_provider() and
of_clk_del_provider()
Sorry for not investigating this before. Just left out from my eyes
somehow.
Actually I can cleanup clk-s2mps11.c driver as well, but only thing is
I can validate it, as I do not have platform to test it.
It should be trivial changes.
If somebody can help me out in validation I can submit the patch for
clk-s2mps11.c driver as well.
Thanks,
Vaibhav
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-22 6:27 UTC|newest]
Thread overview: 48+ 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:06 ` 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-21 11:07 ` Vaibhav Hiremath
2015-07-23 15:52 ` Lee Jones
2015-07-23 15:52 ` Lee Jones
2015-07-23 15:52 ` Lee Jones
2015-08-05 8:53 ` Vaibhav Hiremath
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-21 11:07 ` Vaibhav Hiremath
2015-07-23 5:08 ` Krzysztof Kozlowski
2015-07-23 5:08 ` Krzysztof Kozlowski
2015-07-30 22:13 ` Stephen Boyd
2015-07-30 22:13 ` Stephen Boyd
2015-07-30 22:13 ` Stephen Boyd
2015-07-30 22:21 ` Rob Herring
2015-07-30 22:21 ` Rob Herring
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 11:07 ` Vaibhav Hiremath
2015-07-21 19:10 ` Stephen Boyd
2015-07-21 19:10 ` Stephen Boyd
2015-07-21 19:36 ` Vaibhav Hiremath
2015-07-21 19:36 ` Vaibhav Hiremath
2015-07-21 19:36 ` Vaibhav Hiremath
2015-07-21 20:52 ` Stephen Boyd
2015-07-21 20:52 ` Stephen Boyd
2015-07-22 6:27 ` Vaibhav Hiremath [this message]
2015-07-22 6:27 ` Vaibhav Hiremath
2015-07-22 6:27 ` Vaibhav Hiremath
2015-07-22 6:46 ` Krzysztof Kozlowski
2015-07-22 6:46 ` Krzysztof Kozlowski
2015-07-22 8:16 ` Vaibhav Hiremath
2015-07-22 8:16 ` Vaibhav Hiremath
2015-07-22 22:03 ` Stephen Boyd
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-21 11:07 ` Vaibhav Hiremath
2015-07-23 4:58 ` Krzysztof Kozlowski
2015-07-23 4:58 ` Krzysztof Kozlowski
2015-07-23 4:58 ` Krzysztof Kozlowski
2015-07-23 15:50 ` Lee Jones
2015-07-23 15:50 ` Lee Jones
2015-07-23 15:50 ` Lee Jones
2015-08-05 9:07 ` Vaibhav Hiremath
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=55AF37D9.3000006@linaro.org \
--to=vaibhav.hiremath@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=k.kozlowski@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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.