SUPERH platform development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/3] renesas: change to using clock-indices
Date: Mon, 17 Feb 2014 01:34:22 +0000	[thread overview]
Message-ID: <4598349.vSCyAaeOcD@avalon> (raw)
In-Reply-To: <1392314571-30107-2-git-send-email-ben.dooks@codethink.co.uk>

Hi Geert,

On Saturday 15 February 2014 14:20:16 Geert Uytterhoeven wrote:
> Hi Laurent, Magnus,
> 
> On Fri, Feb 14, 2014 at 3:34 PM, Laurent Pinchart wrote:
> >> >> Regarding how to roll it into the SoC code, I feel that this patch
> >> >> [2/3] and next patch [3/3] potentially causes breakage with the
> >> >> existing binding that was part of the v3.13 upstream kernel.
> >> > 
> >> > If I'm not mistaken that's v3.14, not v3.13.
> >> 
> >> Nope, it's merged in v3.13. Looked it up before sending the email. =)
> > 
> > I might be missing something, but
> > 
> > $ git log v3.13 --oneline -- drivers/clk/shmobile/ | wc
> >       0       0       0
> > 
> > $ git log v3.14-rc1 --oneline -- drivers/clk/shmobile/ | wc
> >       6      48     309
> 
> It's the published bindings that count, right?

I suppose both count, but they've been mainlined at the same time anyway.

> Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.txt
> was added in commit f94859c215b6d977794108a1a9a101239e393c09
> ("clk: shmobile: Add MSTP clock support").
> 
> $ git tag --contains f94859c215b6d977794108a1a9a101239e393c09
> v3.14-rc1
> v3.14-rc2
> $
> 
> Now, the bindings must be in flux, as the documentation doesn't match
> the code, nor the example:
> 
> Documentation says:
> 
> +  - renesas,indices: Indices of the gate clocks into the group (0 to 31)
> 
> Example and implementation use "renesas,clock-indices":
> 
>                 renesas,clock-indices = <
>                         R8A7790_CLK_TPU0 R8A7790_CLK_MMCIF1
> R8A7790_CLK_SDHI3 R8A7790_CLK_SDHI2 R8A7790_CLK_SDHI1 R8A7790_CLK_SDHI0
> R8A7790_CLK_MMCIF0
> 
>                 >;
> 
> Woops...

You don't need to convince me that the DT bindings need time to stabilize :-)

I'll fix this after hearing from Mike on Ben's patches.

-- 
Regards,

Laurent Pinchart


  parent reply	other threads:[~2014-02-17  1:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 18:02 [PATCH 2/3] renesas: change to using clock-indices Ben Dooks
2014-02-14  2:32 ` Magnus Damm
2014-02-14 13:21 ` Laurent Pinchart
2014-02-14 14:03 ` Ben Dooks
2014-02-14 14:28 ` Magnus Damm
2014-02-14 14:34 ` Laurent Pinchart
2014-02-14 14:50 ` Laurent Pinchart
2014-02-15 13:20 ` Geert Uytterhoeven
2014-02-17  1:34 ` Laurent Pinchart [this message]
2014-02-18  1:48 ` Magnus Damm
2014-02-18  1:50 ` Magnus Damm
2014-02-18 12:14 ` Laurent Pinchart
2014-02-19  6:34 ` Magnus Damm
2014-02-19 16:54 ` Laurent Pinchart

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=4598349.vSCyAaeOcD@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