From: leo.yan@linaro.org (Leo Yan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] clk: hisi: add stub clk driver
Date: Fri, 27 Mar 2015 10:08:42 +0800 [thread overview]
Message-ID: <20150327020842.GD4902@leoy-linaro> (raw)
In-Reply-To: <20150326142226.GJ8656@n2100.arm.linux.org.uk>
On Thu, Mar 26, 2015 at 02:22:26PM +0000, Russell King - ARM Linux wrote:
> On Thu, Mar 26, 2015 at 07:13:38PM +0800, Leo Yan wrote:
> > +static unsigned long hisi_stub_clk_recalc_rate(struct clk_hw *hw,
> > + unsigned long parent_rate)
> > +{
> ...
> > + BUG_ON(!stub_clk->lock);
> ...
>
> > +static int hisi_stub_clk_set_rate(struct clk_hw *hw, unsigned long rate,
> > + unsigned long parent_rate)
> > +{
> ...
> > + BUG_ON(!stub_clk->lock);
> ...
>
> > +static long hisi_stub_clk_round_rate(struct clk_hw *hw, unsigned long rate,
> > + unsigned long *parent_rate)
> > +{
> ...
> > + BUG_ON(!stub_clk->lock);
> ...
>
> > +static struct clk_ops hisi_stub_clk_ops = {
> > + .recalc_rate = hisi_stub_clk_recalc_rate,
> > + .round_rate = hisi_stub_clk_round_rate,
> > + .set_rate = hisi_stub_clk_set_rate,
> > +};
> ...
> > +static struct clk *_register_stub_clk(struct device *dev, unsigned int id,
> > + const char *name, const char *parent_name, unsigned long flags,
> > + spinlock_t *lock)
> > +{
> > + struct hisi_stub_clk *stub_clk;
> > + struct clk *clk;
> > + struct clk_init_data init;
> > +
> > + stub_clk = kzalloc(sizeof(*stub_clk), GFP_KERNEL);
> > + if (!stub_clk) {
> > + pr_err("%s: fail to alloc stub clk!\n", __func__);
> > + return ERR_PTR(-ENOMEM);
> > + }
> > +
> > + init.name = name;
> > + init.ops = &hisi_stub_clk_ops;
> > + init.parent_names = parent_name ? &parent_name : NULL;
> > + init.num_parents = parent_name ? 1 : 0;
> > + init.flags = flags;
> > +
> > + stub_clk->hw.init = &init;
> > + stub_clk->id = id;
> > + stub_clk->lock = lock;
>
> Under what scenario is it safe to call _register_stub_clk() with a NULL
> lock argument?
>
> If lock is NULL, then every function callable via the ops structure
> will bug.
>
> Rather than doing a test in each method function, do it in
> _register_stub_clk() - this means we aren't waiting for a NULL pointer
> deref when one of these method functions gets called.
Will fix to check lock pointer in the function _register_stub_clk().
Thanks,
Leo Yan
next prev parent reply other threads:[~2015-03-27 2:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 11:13 [PATCH 0/4] clk: hisilicon: support stub clock Leo Yan
2015-03-26 11:13 ` [PATCH 1/4] clk: hisi: add API for allocation clk data struct Leo Yan
2015-03-26 14:18 ` Russell King - ARM Linux
2015-03-27 1:48 ` Leo Yan
2015-03-26 11:13 ` [PATCH 2/4] dt-bindings: clk: hisilicon: Document stub clock driver Leo Yan
2015-03-26 11:13 ` [PATCH 3/4] clk: hisi: add stub clk driver Leo Yan
2015-03-26 14:22 ` Russell King - ARM Linux
2015-03-27 2:08 ` Leo Yan [this message]
2015-03-26 11:13 ` [PATCH 4/4] clk: hisi: add stub clock register function Leo Yan
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=20150327020842.GD4902@leoy-linaro \
--to=leo.yan@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).