From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/2] clk: shmobile: Fix MSTP clock array initialization
Date: Thu, 09 Jan 2014 17:53:43 +0000 [thread overview]
Message-ID: <3278719.rAcIQXV7lu@avalon> (raw)
In-Reply-To: <1388167599-23525-3-git-send-email-valentine.barshak@cogentembedded.com>
Hi Valentine,
On Thursday 09 January 2014 21:51:05 Valentine wrote:
> On 01/09/2014 09:46 PM, Laurent Pinchart wrote:
> > On Saturday 28 December 2013 12:35:31 Laurent Pinchart wrote:
> >> On Friday 27 December 2013 22:06:39 Valentine Barshak wrote:
> >>> The clks member of the clk_onecell_data structure should
> >>> point to a valid clk array (no NULL entries allowed),
> >>> and the clk_num should be equal to the number
> >>> of elements in the clks array.
> >>>
> >>> The MSTP driver fails to satisfy the above conditions.
> >>> The clks array may contain NULL entries if not all
> >>> clock-indices are initialized in the device tree.
> >>> Thus, if the clock indices are interleaved we end up
> >>> with NULL pointers in-between.
> >>
> >> I don't think that's an issue in practice as long as no reference to a
> >> NULL clock exists in the device tree, but it should of course be fixed.
> >>
> >>> The other problem is the driver uses maximum clock index
> >>> as the number of clocks, which is incorrect (less than
> >>> the actual number of clocks by 1).
> >>
> >> Good catch.
> >>
> >>> Fix the first issue by pre-setting the whole clks array
> >>> with ERR_PTR(-ENOENT) pointers instead of zeros; and
> >>> use maximum clkidx + 1 as the number of clocks to fix
> >>> the other one.
> >>>
> >>> This should make of_clk_src_onecell_get() return the following:
> >>> * valid clk pointers for all clocks registered;
> >>> * ERR_PTR(-EINVAL) if (idx >= clk_data->clk_num);
> >>> * ERR_PTR(-ENOENT) if the clock at the selected index was not
> >>>
> >>> initialized in the device tree (and was not registered).
> >>>
> >>> Signed-off-by: Valentine Barshak <valentine.barshak@cogentembedded.com>
> >>> ---
> >>>
> >>> drivers/clk/shmobile/clk-mstp.c | 9 +++++++--
> >>> 1 file changed, 7 insertions(+), 2 deletions(-)
> >>>
> >>> diff --git a/drivers/clk/shmobile/clk-mstp.c
> >>> b/drivers/clk/shmobile/clk-mstp.c index be7d017..14b91ad 100644
> >>> --- a/drivers/clk/shmobile/clk-mstp.c
> >>> +++ b/drivers/clk/shmobile/clk-mstp.c
> >>> @@ -160,7 +160,7 @@ static void __init cpg_mstp_clocks_init(struct
> >>> device_node *np)
> >>>
> >>> unsigned int i;
> >>>
> >>> group = kzalloc(sizeof(*group), GFP_KERNEL);
> >>>
> >>> - clks = kzalloc(MSTP_MAX_CLOCKS * sizeof(*clks), GFP_KERNEL);
> >>> + clks = kmalloc(MSTP_MAX_CLOCKS * sizeof(*clks), GFP_KERNEL);
> >>>
> >>> if (group = NULL || clks = NULL) {
> >>>
> >>> kfree(group);
> >>> kfree(clks);
> >>>
> >>> @@ -182,6 +182,10 @@ static void __init cpg_mstp_clocks_init(struct
> >>> device_node *np) }
> >>>
> >>> for (i = 0; i < MSTP_MAX_CLOCKS; ++i) {
> >>>
> >>> + clks[i] = ERR_PTR(-ENOENT);
> >>> + }
> >>
> >> No need for brackets here.
> >>
> >> With this fixed,
> >>
> >> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> >
> > Could you please resubmit the series with this fixed and the Reviewed-by
> > line from Ben picked for patch 1/2, and ask Mike to apply it for v3.14 in
> > the cover letter ?
>
> I did respin these here:
> http://marc.info/?l=linux-sh&m\x138823255807611&w=2
Oops, my bad, I've missed that.
> Mike said he had taken them in clk-next,
Great, thank you.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-01-09 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 18:06 [PATCH 2/2] clk: shmobile: Fix MSTP clock array initialization Valentine Barshak
2013-12-28 11:35 ` Laurent Pinchart
2014-01-09 17:46 ` Laurent Pinchart
2014-01-09 17:51 ` Valentine
2014-01-09 17:53 ` Laurent Pinchart [this message]
2014-01-09 18:12 ` Valentine
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=3278719.rAcIQXV7lu@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.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).