All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Turquette <mturquette@linaro.org>
To: Tony Lindgren <tony@atomide.com>, "Stephen Boyd" <sboyd@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/2] Minimal FAPLL clock support for dm816x
Date: Wed, 14 Jan 2015 14:06:49 -0800	[thread overview]
Message-ID: <20150114220649.22722.26307@quantum> (raw)
In-Reply-To: <1421189488-9657-1-git-send-email-tony@atomide.com>

Quoting Tony Lindgren (2015-01-13 14:51:26)
> Hi all,
> 
> Here's a minimal support for the FAPLL (Flying Adder PLL) on dm816x
> which is a omap variant.

Tony,

Patches look fine to me. I'll give it a few days for Paul or Tero to
comment if they have any concerns.

Also, "flying adder pll" is a pretty badass pll name.

Regards,
Mike

> 
> Regards,
> 
> Tony
> 
> 
> Tony Lindgren (2):
>   clk: ti: Add support for FAPLL on dm816x
>   clk: ti: Initialize clocks for dm816x
> 
>  .../devicetree/bindings/clock/ti/fapll.txt         |  33 ++
>  drivers/clk/ti/Makefile                            |   1 +
>  drivers/clk/ti/clk-3xxx.c                          |   8 +-
>  drivers/clk/ti/clk-816x.c                          |  53 +++
>  drivers/clk/ti/fapll.c                             | 410 +++++++++++++++++++++
>  5 files changed, 498 insertions(+), 7 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/clock/ti/fapll.txt
>  create mode 100644 drivers/clk/ti/clk-816x.c
>  create mode 100644 drivers/clk/ti/fapll.c
> 
> -- 
> 2.1.4
> 

  parent reply	other threads:[~2015-01-14 22:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 22:51 [PATCH 0/2] Minimal FAPLL clock support for dm816x Tony Lindgren
2015-01-13 22:51 ` [PATCH 1/2] clk: ti: Add support for FAPLL on dm816x Tony Lindgren
2015-01-13 22:51 ` [PATCH 2/2] clk: ti: Initialize clocks for dm816x Tony Lindgren
2015-01-14 22:06 ` Mike Turquette [this message]
2015-01-19 16:36   ` [PATCH 0/2] Minimal FAPLL clock support " Mike Turquette

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=20150114220649.22722.26307@quantum \
    --to=mturquette@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=tony@atomide.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.