linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 01/04] ARM: shmobile: Initial r8a7791 SoC support
Date: Wed, 18 Sep 2013 17:20:00 +0000	[thread overview]
Message-ID: <20130918172000.GA27340@quad.lixom.net> (raw)
In-Reply-To: <CANqRtoQ0dnG6HwjJSrK8+Qt8wvJhqsJHxgj-LGvnJvS0KT81nw@mail.gmail.com>

Hi,

Coming across this somewhat old email thread, apologies for the delay in
response.

On Mon, Sep 09, 2013 at 05:05:18PM +0900, Magnus Damm wrote:
> On Mon, Sep 9, 2013 at 4:45 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
> > On Mon, Sep 9, 2013 at 9:21 AM, Magnus Damm <magnus.damm@gmail.com> wrote:
> >
> >> Fortunately there are plans to convert several mach-shmobile SoCs to
> >> common clocks over the next 6 months. As you know, we spent much time
> >> and efforts converting to pinctrl last two 6 month periods, and now we
> >> will be targeting common clocks.
> >
> > I trust you on this, it's not for me to decide but for the ARM SoC
> > maintainers. I think Arnd basically said at one point that it is OK
> > to add some new cruft as long as you remove more old cruft at
> > the same time, so I guess you will have to make an argument that
> > this is happening.
> 
> Yeah, I agree. I hope to discuss this in person later this Autumn.
> 
> >> There are several incremental patches available for r8a7791, but since
> >> this is a new and rare platform it won't be the first SoC we convert
> >> to common clocks. So CCF development will happen on r8a7791, but it
> >> won't be the first platform.
> >
> > This is pretty much the inverse argument of the usual stance of
> > the ARM SoC tree - usually we ask that new platforms should use
> > new frameworks. I do understand it from a practical point of view,
> > that new SoCs only exist in few prototypes.
> 
> I suppose negotiation has to happen on some level, and I appreciate
> the higher level give-and-take approach that Arnd has been taking. At
> this time though, apart from common clocks, extended DT support and
> multiplatform I'm not so sure what desired cleanup-wise.

We have definitely been OK with new code going in together with cleanups,
but I think we're reaching a point where there's a lot of new code going
in on shmobile platforms now, and we've had some growing pains on the
platform for it -- conflicts with other maintainer trees because they have
picked up board file changes, etc.

I think much of this wouldn't be a problem if the conversions to
DT/multiplatform was completed, so it would be great if the conversion
could be given priority on the Renesas side, especially given the rate
of new additions as of late -- I think we're seeing new SoCs almost
every release cycle as of late.

So, bottom line: I'm not going to refuse taking this new platform,
but you're close to the limits and please try to prioritize finishing
conversion.  In particular since all this "new legacy code" you're adding
will all have to be converted soon -- in some cases it might be better
to wait with adding it until after conversion.


-Olof

  parent reply	other threads:[~2013-09-18 17:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04  3:45 [PATCH 00/04] ARM: shmobile: Initial r8a7791 SoC and Koelsch board support Magnus Damm
2013-09-04  3:45 ` [PATCH 01/04] ARM: shmobile: Initial r8a7791 SoC support Magnus Damm
2013-09-06 16:21   ` Linus Walleij
2013-09-09  0:16     ` Simon Horman
2013-09-09  6:55       ` Linus Walleij
2013-09-09  7:37         ` Magnus Damm
2013-09-09  7:21     ` Magnus Damm
2013-09-09  7:45       ` Linus Walleij
2013-09-09  8:05         ` Magnus Damm
2013-09-09  9:15           ` Linus Walleij
2013-09-09 10:32             ` Magnus Damm
2013-09-18 17:20           ` Olof Johansson [this message]
2013-09-04  3:46 ` [PATCH 02/04] ARM: shmobile: r8a7791 SCIF support Magnus Damm
2013-09-06 16:27   ` Linus Walleij
2013-09-09  0:15     ` Simon Horman
2013-09-09  6:54       ` Linus Walleij
2013-09-09  7:09         ` Simon Horman
2013-09-09  7:28           ` Magnus Damm
2013-09-09  7:24     ` Magnus Damm
2013-09-04  3:46 ` [PATCH 03/04] ARM: shmobile: r8a7791 CMT support Magnus Damm
2013-09-04  3:46 ` [PATCH 04/04] ARM: shmobile: Koelsch support Magnus Damm
2013-09-04  8:38 ` [PATCH 00/04] ARM: shmobile: Initial r8a7791 SoC and Koelsch board support Simon Horman
2013-09-06  7:09   ` Simon Horman
2013-09-09  7:39     ` Magnus Damm

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=20130918172000.GA27340@quad.lixom.net \
    --to=olof@lixom.net \
    --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).