linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 01/04] ARM: shmobile: Initial r8a7791 SoC support
Date: Mon, 09 Sep 2013 07:37:34 +0000	[thread overview]
Message-ID: <CANqRtoQirDKYS-vGH-pbrXH52WWDe8q77XzdLBGApbf5XRkH=w@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdacYC-CKbr-=pzN=nLWgBqk4CCQS3rG8LDASKjg3uBP=Q@mail.gmail.com>

Hi Linus,

On Mon, Sep 9, 2013 at 3:55 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Mon, Sep 9, 2013 at 2:16 AM, Simon Horman <horms@verge.net.au> wrote:
>
>> So on those two counts my preference would be for any enhancements
>> to be done as incremental patches on top of this series.
>
> Again: do such enhancements even exist?

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.

To be able to start using common clocks we first need to break out the
basic building blocks and then tie them in on one SoC at a time. These
basic building blocks of course need to use already-existing CCF bits
for gating, dividers and plls. We will also need some special handling
like for instance polling of registers to wait for rate change.

So the issue in my opinion is not so much the SoC specific bits.
Instead it's the shared CCF bits that need work. The real question is
probably if new SoC support needs to block on framework support. I'm
all about incremental changes. If there is something special that
needs extra focus then of course we will work on that.

Cheers,

/ magnus

  reply	other threads:[~2013-09-09  7:37 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 [this message]
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
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='CANqRtoQirDKYS-vGH-pbrXH52WWDe8q77XzdLBGApbf5XRkH=w@mail.gmail.com' \
    --to=magnus.damm@gmail.com \
    --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).