linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: cavokz@gmail.com (Domenico Andreoli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: Use a separate struct for holding init data.
Date: Fri, 4 May 2012 01:03:08 +0200	[thread overview]
Message-ID: <20120503230308.GA13016@glitch> (raw)
In-Reply-To: <1335419936-10881-1-git-send-email-skannan@codeaurora.org>

On Wed, Apr 25, 2012 at 10:58:56PM -0700, Saravana Kannan wrote:
>
> diff --git a/drivers/clk/clk-divider.c b/drivers/clk/clk-divider.c
> index 90627e4..8ea11b4 100644
> --- a/drivers/clk/clk-divider.c
> +++ b/drivers/clk/clk-divider.c
> @@ -167,6 +167,7 @@ struct clk *clk_register_divider(struct device *dev, const char *name,
>  {
>  	struct clk_divider *div;
>  	struct clk *clk;
> +	struct clk_init_data init;
>  
>  	/* allocate the divider */
>  	div = kzalloc(sizeof(struct clk_divider), GFP_KERNEL);
> @@ -175,19 +176,22 @@ struct clk *clk_register_divider(struct device *dev, const char *name,
>  		return ERR_PTR(-ENOMEM);
>  	}
>  
> +	init.name = name;
> +	init.ops = &clk_divider_ops;
> +	init.flags = flags;
> +	init.parent_names = (parent_name ? &parent_name: NULL);
> +	init.num_parents = (parent_name ? 1 : 0);
> +
>  	/* struct clk_divider assignments */
>  	div->reg = reg;
>  	div->shift = shift;
>  	div->width = width;
>  	div->flags = clk_divider_flags;
>  	div->lock = lock;
> +	div->hw.init = &init;
>  
>  	/* register the clock */
> -	clk = clk_register(dev, name,
> -			&clk_divider_ops, &div->hw,
> -			(parent_name ? &parent_name: NULL),
> -			(parent_name ? 1 : 0),
> -			flags);
> +	clk = clk_register(dev, &div->hw);
>  
>  	if (IS_ERR(clk))
>  		kfree(div);

I would prefer to rip the parent _settings_ configuration out of
clk_register(). It's optional right? And passing a single parent is a
common case.

Three cases:

  1) one parent:
     __clk_register_parent(clk, parent_name);
     clk_register(dev, name, &ops, flags);

  2) many parents:
     __clk_register_parents(clk, parent_names, num_parents);
     clk_register(dev, name, &ops, flags);

  3) no parents:
     clk_register(dev, name, &ops, flags);

You may also want to move the whole parent initialization into
__clk_register_parents() and call it after clk_register(), it would
simplify some error paths.

This pattern could be used also with other common clocks registration
functions (fixed rate, divider, mux, etc) that may have complex
initializations and/or optional parameters that cannot go all on the
same function call.

cheers,
Domenico

  parent reply	other threads:[~2012-05-03 23:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26  5:58 [PATCH] clk: Use a separate struct for holding init data Saravana Kannan
2012-04-26  6:28 ` Saravana Kannan
2012-04-26  8:42   ` Sascha Hauer
2012-04-26  9:36     ` Saravana Kannan
2012-04-26  9:51       ` Sascha Hauer
2012-04-30 19:30         ` Saravana Kannan
2012-04-30 22:19           ` Turquette, Mike
2012-04-30 22:46             ` Saravana Kannan
2012-05-01  8:11               ` Shawn Guo
2012-05-01  9:13                 ` Andrew Lunn
2012-05-01 17:00                   ` Mark Brown
2012-05-01 18:03                     ` Saravana Kannan
2012-05-01 18:19                       ` Mark Brown
2012-05-02  1:56                         ` Mike Turquette
2012-05-02  2:14                           ` Shawn Guo
2012-05-02  5:16                           ` Andrew Lunn
2012-05-02 19:19                             ` Mike Turquette
2012-05-02 13:32                           ` Arnd Bergmann
2012-05-02 15:28                           ` Mark Brown
2012-05-01 18:04                     ` Andrew Lunn
2012-04-26  8:39 ` Sascha Hauer
2012-04-26  9:15   ` Saravana Kannan
2012-04-26  9:49   ` Mark Brown
2012-05-02  2:04 ` Mike Turquette
2012-05-02  4:42   ` Saravana Kannan
2012-05-02 19:07     ` Mike Turquette
2012-05-02  9:58 ` Sascha Hauer
2012-05-02 10:02   ` Russell King - ARM Linux
2012-05-02 10:11     ` Sascha Hauer
2012-05-03 23:03 ` Domenico Andreoli [this message]
2012-05-04  1:11   ` Saravana Kannan
2012-05-04  6:50     ` Domenico Andreoli

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=20120503230308.GA13016@glitch \
    --to=cavokz@gmail.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).