linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/3] clk: emev2: Add support for emev2 SMU clocks with DT
Date: Wed, 09 Oct 2013 03:38:11 +0000	[thread overview]
Message-ID: <20131009033807.GM15065@verge.net.au> (raw)
In-Reply-To: <CANqRtoRZM=5FYG7+fq5c+TQEuHtJRmcGP1CmMq5kO5Ayvg=W6w@mail.gmail.com>

On Tue, Oct 08, 2013 at 02:58:08PM +0900, Magnus Damm wrote:
> On Tue, Oct 8, 2013 at 2:32 PM,  <takasi-y@ops.dti.ne.jp> wrote:
> > Device tree clock binding document for EMMA Mobile EV2 SMU,
> > And Common clock framework based implementation of it.
> > Following nodes are defined to describe clock tree.
> > - renesas,emev2-smu
> > - renesas,emev2-smu-clkdiv
> > - renesas,emev2-smu-gclk
> >
> > These bindings are designed manually based on
> >  19UH0037EJ1000_SMU : System Management Unit User's Manual
> >
> > So far, reparent is not implemented, and is fixed to index #0.
> > Clock tree description is not included, and should be provided
> > by device-tree.
> >
> > Signed-off-by: Takashi Yoshii <takasi-y@ops.dti.ne.jp>
> > ---
> >  .../devicetree/bindings/clock/emev2-clock.txt      |  98 +++++++++++++++++++
> >  drivers/clk/Makefile                               |   1 +
> >  drivers/clk/shmobile/Makefile                      |   3 +
> >  drivers/clk/shmobile/clk-emev2.c                   | 104 +++++++++++++++++++++
> >  4 files changed, 206 insertions(+)
> 
> Thanks for cleaning up the Makefile bits, Yoshii-san.
> 
> This patch and the bindings look fine to me from a SoC point of view.
> Using these together with the topology information in emev2.dtsi makes
> it possible for us to use CCF and multiplatform as expected on the
> EMEV2 SoC.
> 
> Acked-by: Magnus Damm <damm@opensource.se>

Thanks. I will send a pull request for this change to Mike Turquette.

  reply	other threads:[~2013-10-09  3:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08  5:30 [PATCH v2 0/3] ARM: shmobile: kzm9d: migrate to common clock framework with DT takasi-y
2013-10-08  5:32 ` [PATCH v2 1/3] clk: emev2: Add support for emev2 SMU clocks " takasi-y
2013-10-08  5:58   ` Magnus Damm
2013-10-09  3:38     ` Simon Horman [this message]
2013-10-09  6:10       ` Ben Dooks
2013-10-08  5:33 ` [PATCH v2 2/3] ARM: shmobile: emev2: Add clock tree description in DT takasi-y
2013-10-08  5:54   ` Magnus Damm
2013-10-09  3:40     ` Simon Horman
2013-10-08  5:34 ` [PATCH v2 3/3] ARM: shmobile: kzm9d: Use common clock framework takasi-y
2013-10-08  5:52   ` Magnus Damm
2013-10-09  3:40   ` Simon Horman
2013-10-09  4:59     ` Magnus Damm
2013-10-09  6:54       ` Simon Horman
2013-10-09  7:29         ` Magnus Damm
2013-10-09 10:39           ` Simon Horman
2013-10-29  4:42             ` Simon Horman
2013-12-02  2:25               ` Simon Horman
2013-12-23  6:41                 ` Mike Turquette
2013-12-23  8:00                   ` Simon Horman
2014-01-06  8:10                     ` 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=20131009033807.GM15065@verge.net.au \
    --to=horms@verge.net.au \
    --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).