linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 00/10] sh73a0 common clock framework implementation
Date: Wed, 03 Sep 2014 00:09:15 +0000	[thread overview]
Message-ID: <20140903000915.GF23704@verge.net.au> (raw)
In-Reply-To: <1409649186-1046-1-git-send-email-ulrich.hecht+renesas@gmail.com>

On Tue, Sep 02, 2014 at 11:12:56AM +0200, Ulrich Hecht wrote:
> Hi!
> 
> Here's an updated sh73a0 CCF implementation.  It adds the missing clock
> assignments, CMT1, and various minor fixes.  It also splits off the parent
> selection for the DIV6 clocks so it can be merged without requiring the DIV6
> driver patch.
> 
> CU
> Uli
> 
> 
> Changes since v1:
> - div6 patch replaced with v4
> - split off div6 extended clocks
> - added cmt1 DT description
> - added MSTP clock assignments
> - reordered according to dependencies
> - removed dummy frequencies in extal2, extcki
> - removed enable_on_init on zb1 and flctlck
> - added missing tpu4 in mstp3_clks
> - use c->parent in cpg driver
> - fix some style issues
> 
> 
> Ulrich Hecht (10):
>   clk: shmobile: sh73a0 common clock framework implementation
>   ARM: shmobile: sh73a0: Common clock framework DT description
>   ARM: shmobile: sh73a0: common clock framework board support
>   ARM: shmobile: sh73a0: add MSTP clock assignments to DT
>   ARM: shmobile: sh73a0: Add CMT1 device to DT
>   ARM: shmobile: kzm9g-reference: Enable CMT1 in device tree
>   ARM: shmobile: kzm9g: require ZB1 clock for Ethernet controller
>   clk: shmobile: Add r8a7740, sh73a0 SoCs to MSTP bindings
>   clk: shmobile: div6: support selectable-input clocks
>   ARM: shmobile: sh73a0: add selectable sources to DIV6 clocks

Hi Ulrich,

in general this seems nice to me. I have a few observations:

* It looks like some of the "ARM: shmobile:" patches,
  especially patches 2 - 7, may break bisection. If
  so could you re-arrange the patches to avoid this?

* It looks like you are enabling CMT1. Thanks for that,
  for some reason I thought that I had already handled that: it seems not.

* Would it be useful if I made a series on top of your series
  to enable serial via DT. Again, I thought I had already handled
  that too but it seems I haven't.

  reply	other threads:[~2014-09-03  0:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02  9:12 [PATCH v2 00/10] sh73a0 common clock framework implementation Ulrich Hecht
2014-09-03  0:09 ` Simon Horman [this message]
2014-09-03  8:05 ` Ulrich Hecht
2014-09-04  7:09 ` Simon Horman

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=20140903000915.GF23704@verge.net.au \
    --to=horms@verge.net.au \
    --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).