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: Fri, 14 Feb 2014 13:21:55 +0000	[thread overview]
Message-ID: <1746722.QNgDfvocK0@avalon> (raw)
In-Reply-To: <1392314571-30107-2-git-send-email-ben.dooks@codethink.co.uk>

Hi Magnus,

On Friday 14 February 2014 11:32:08 Magnus Damm wrote:
> On Fri, Feb 14, 2014 at 3:02 AM, Ben Dooks wrote:
> > With the addition of clock-indices, we need to change the renesas
> > clock implementation to use these instead of the local definition.
> > 
> > Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> > ---
> > 
> >  .../bindings/clock/renesas,cpg-mstp-clocks.txt   |  2 +-
> >   arch/arm/boot/dts/r8a7790.dtsi                  | 16 ++++++++--------
> >  arch/arm/boot/dts/r8a7791.dtsi                   | 18 +++++++++---------
> >  drivers/clk/shmobile/clk-mstp.c                  |  2 +-
> >  4 files changed, 19 insertions(+), 19 deletions(-)
> 
> Thanks for your patches! Good to see more common bindings.
> 
> 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.

> I'd like to maintain backwards compatibility for our users. Also, this patch
> crosses subsystems which may not be entirely ideal from a merge perspective.
> 
> If other people in the community agree with [1/3] then may I propose that
> you rework the series into:
> 
> [1/3] as-is is fine for me
> [2/3] clk-mstp and documentation changes only - Take the clk-mstp.c
> code from [2/3] and merge with [3/3], stay backwards compatible.
> [3/3] adjust the SoC DTS
> 
> That would maintain backwards compatibility and keep existing users happy.

We'll have to address this DT backward compatibility nonsense at some point. 
We can't consider all bindings as stable as soon as they hit mainline, that 
just won't fly. In this particular case, given that the driver got merged in 
v3.14-rc1, and that our mainline multiplatform boards in mainline are 
virtually useless in real products given their early stage of development, I 
would rather consider the clocks DT bindings as unstable for at least a couple 
more kernel versions.

-- 
Regards,

Laurent Pinchart


  parent reply	other threads:[~2014-02-14 13:21 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 [this message]
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
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=1746722.QNgDfvocK0@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