From: Sergej Sawazki <ce3a@gmx.de>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: mturquette@linaro.org, jsarha@ti.com, linux-clk@vger.kernel.org
Subject: Re: [PATCH v2] clk: add gpio controlled clock multiplexer
Date: Sun, 07 Jun 2015 21:15:30 +0200 [thread overview]
Message-ID: <55749852.70909@gmx.de> (raw)
In-Reply-To: <20150604214616.GS676@codeaurora.org>
On Thu, 4 Jun 2015 14:46:16 -0700, Stephen Boyd wrote:
> On 05/24, Sergej Sawazki wrote:
>> + * Gpio controlled clock multiplexer implementation
>> + */
>> +
>> +#include <linux/clk-provider.h>
>> +#include <linux/module.h>
>
> What's module.h used for? We need export.h for the
> EXPORT_SYMBOL_GPL usage though.
>
I will fix it in v3, thanks.
>> +#include <linux/slab.h>
>> +#include <linux/gpio.h>
>> +#include <linux/gpio/consumer.h>
>> +#include <linux/of_gpio.h>
>
> Do we need the of_gpio include? We can't get everything we need
> from gpio/consumer.h?
>
We need of_gpio.h because of of_gpio_flags, but we can delete
gpio.h and gpio/consumer.h.
>> + struct clk_init_data init = { NULL };
>
> struct clk_init_data init = { }
>
> is preferred style.
>
OK.
>> + if (dev)
>> + clk_gpio_mux = devm_kzalloc(dev, sizeof(struct clk_gpio_mux),
>
> sizeof(*clk_gpio_mux)
>
> is preferred style
>
OK.
>> + GFP_KERNEL);
>> + else
>> + clk_gpio_mux = kzalloc(sizeof(struct clk_gpio_mux), GFP_KERNEL);
>> +
>
> ditto.
>
OK.
>
> Please find a way to share most of this code with the other gpio
> based clock provider. Putting the two types of gpio clocks into the
> same file would probably work.
>
I will try and resend as v3. Thanks for you comments.
Sergej
prev parent reply other threads:[~2015-06-07 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 9:01 [PATCH v2] clk: add gpio controlled clock multiplexer Sergej Sawazki
2015-06-04 21:46 ` Stephen Boyd
2015-06-07 19:15 ` Sergej Sawazki [this message]
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=55749852.70909@gmx.de \
--to=ce3a@gmx.de \
--cc=jsarha@ti.com \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@linaro.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.