public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sugaya, Taichi" <sugaya.taichi@socionext.com>
To: Stephen Boyd <sboyd@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org
Cc: Michael Turquette <mturquette@baylibre.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Russell King <linux@armlinux.org.uk>,
	Jiri Slaby <jslaby@suse.com>,
	Masami Hiramatsu <masami.hiramatsu@linaro.org>,
	Jassi Brar <jaswinder.singh@linaro.org>
Subject: Re: [PATCH 07/14] clock: milbeaut: Add Milbeaut M10V clock control
Date: Fri, 28 Dec 2018 15:38:58 +0900	[thread overview]
Message-ID: <0c8db56a-6738-e003-5088-0c13588f695a@socionext.com> (raw)
In-Reply-To: <154595756614.179992.794211301759568891@swboyd.mtv.corp.google.com>

Hi

On 2018/12/28 9:39, Stephen Boyd wrote:
> Quoting Sugaya, Taichi (2018-12-25 17:35:27)
>> Hi
>>
>> On 2018/11/30 17:31, Stephen Boyd wrote:
>>>> +       init.num_parents = parents;
>>>> +       init.parent_names = parent_names;
>>>> +
>>>> +       mcm->cname = clk_name;
>>>> +       mcm->parent = 0;
>>>> +       mcm->hw.init = &init;
>>>> +
>>>> +       clk = clk_register(NULL, &mcm->hw);
>>>> +       if (IS_ERR(clk))
>>>> +               goto err_clk;
>>>> +
>>>> +       of_clk_add_provider(node, of_clk_src_simple_get, clk);
>>>> +       return;
>>>> +
>>>> +err_clk:
>>>> +       kfree(mcm);
>>>> +err_mcm:
>>>> +       kfree(parent_names);
>>>> +}
>>>> +CLK_OF_DECLARE(m10v_clk_mux, "socionext,milbeaut-m10v-clk-mux",
>>>> +                       m10v_clk_mux_setup);
>>>
>>> Any chance you can use a platform driver?
>>>
>>
>> Excuse me to re-ask you.
>> Why do you recommend to use a platform driver? Is that current fad?
> 
> Not exactly a fad. We've been doing it for some time now. From an older
> email on the list:
> 
> Reasons (in no particular order):
> 
>    1. We get a dev pointer to use with clk_hw_register()
> 
>    2. We can handle probe defer if some resource is not available
> 
>    3. Using device model gets us a hook into power management frameworks
>       like runtime PM and system PM for things like suspend and hibernate
> 
>    4. It encourages a single DT node clk controller style binding
>       instead of a single node per clk style binding
> 
>    5. We can use non-DT specific functions like devm_ioremap_resource() to map
>       registers and acquire other resources, leading to more portable and
>       generic code
> 
>    6. We may be able to make the device driver a module, which will
>       make distros happy if we don't have to compile in all
>       these clk drivers to the resulting vmlinux
> 

Great thanks for answering. I strongly understand.
#It takes a bit of time to send v2.

Best Regards,
Sugaya Taichi


  reply	other threads:[~2018-12-28  6:39 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19  1:01 [PATCH 00/14] Add basic support for Socionext Milbeaut M10V SoCs Sugaya Taichi
2018-11-19  1:01 ` [PATCH 01/14] ARM: milbeaut: Add basic support for Milbeaut m10v SoC Sugaya Taichi
2018-11-19 16:24   ` Rob Herring
2018-11-21  9:33     ` sugaya.taichi
2018-11-19  1:01 ` [PATCH 02/14] dt-bindings: soc: milbeaut: Add Milbeaut trampoline description Sugaya Taichi
2018-11-28  2:01   ` Stephen Boyd
2018-11-29 12:24     ` Sugaya, Taichi
2018-11-30  8:16       ` Stephen Boyd
2018-12-03  7:42         ` Sugaya, Taichi
2018-12-03 15:49           ` Rob Herring
2018-12-04 11:30             ` Sugaya, Taichi
2018-12-04 13:32               ` Rob Herring
2018-12-05 10:30                 ` Sugaya, Taichi
2019-01-22 11:36                 ` Sugaya, Taichi
2019-01-22 11:50                   ` Russell King - ARM Linux admin
2019-01-29  8:28                     ` Sugaya, Taichi
2019-01-30  8:40                       ` Russell King - ARM Linux admin
2018-11-19  1:01 ` [PATCH 03/14] ARM: milbeaut: Add Milbeaut M10V early printk Sugaya Taichi
2018-11-19 15:21   ` Rob Herring
2018-11-21  4:07     ` sugaya.taichi
2018-11-19  1:01 ` [PATCH 04/14] dt-bindings: timer: Add Milbeaut M10V timer description Sugaya Taichi
2018-12-04 23:03   ` Rob Herring
2018-12-06  7:42     ` Sugaya, Taichi
2018-11-19  1:01 ` [PATCH 05/14] clocksource/drivers/timer-milbeaut: Add Milbeaut M10V timer Sugaya Taichi
2018-11-21 10:08   ` Daniel Lezcano
2018-11-22  2:23     ` Sugaya, Taichi
2018-11-19  1:01 ` [PATCH 06/14] dt-bindings: clock: milbeaut: add Milbeaut clock description Sugaya Taichi
2018-11-30  8:19   ` Stephen Boyd
2018-12-03  8:08     ` Sugaya, Taichi
2018-11-19  1:01 ` [PATCH 07/14] clock: milbeaut: Add Milbeaut M10V clock control Sugaya Taichi
2018-11-30  8:31   ` Stephen Boyd
2018-12-04  8:26     ` Sugaya, Taichi
2018-12-04 18:15       ` Stephen Boyd
2018-12-05 11:42         ` Sugaya, Taichi
2018-12-04 11:03     ` Masahiro Yamada
2018-12-04 18:14       ` Stephen Boyd
2018-12-05  4:26         ` Masahiro Yamada
2018-12-05  6:57           ` Stephen Boyd
2018-12-26  1:35     ` Sugaya, Taichi
2018-12-28  0:39       ` Stephen Boyd
2018-12-28  6:38         ` Sugaya, Taichi [this message]
2018-11-19  1:01 ` [PATCH 08/14] dt-bindings: serial: Add Milbeaut M10V serial description Sugaya Taichi
2018-11-19  1:01 ` [PATCH 09/14] serial: Add Milbeaut M10V serial control Sugaya Taichi

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=0c8db56a-6738-e003-5088-0c13588f695a@socionext.com \
    --to=sugaya.taichi@socionext.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jaswinder.singh@linaro.org \
    --cc=jslaby@suse.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=masami.hiramatsu@linaro.org \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=tglx@linutronix.de \
    /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