From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Chen-Yu Tsai <wens@csie.org>
Cc: Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Jens Kuske <jenskuske@gmail.com>,
Vishnu Patekar <vishnupatekar0510@gmail.com>,
Hans de Goede <hdegoede@redhat.com>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
Jean-Francois Moine <moinejf@free.fr>
Subject: Re: [PATCH v4] clk: sunxi: Refactor A31 PLL6 so that it can be reused
Date: Thu, 4 Feb 2016 13:05:07 +0100 [thread overview]
Message-ID: <20160204120507.GC4270@lukather> (raw)
In-Reply-To: <1454358000-13594-1-git-send-email-maxime.ripard@free-electrons.com>
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
On Mon, Feb 01, 2016 at 09:20:00PM +0100, Maxime Ripard wrote:
> Remove the fixed dividers from the PLL6 driver to be able to have a
> reusable driver that can be used across several SoCs that share the same
> controller, but don't have the same set of dividers for this clock, and to
> also be reused multiple times in the same SoC, since we're droping the
> clock name.
>
> Acked-by: Chen-Yu Tsai <wens@csie.org>
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Applied.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-04 12:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 20:20 [PATCH v4] clk: sunxi: Refactor A31 PLL6 so that it can be reused Maxime Ripard
2016-02-04 12:05 ` Maxime Ripard [this message]
2016-02-04 15:25 ` Jean-Francois Moine
2016-02-10 12:53 ` Maxime Ripard
2016-02-10 17:04 ` Jean-Francois Moine
2016-02-11 9:53 ` Maxime Ripard
2016-02-05 17:59 ` Andre Przywara
2016-02-10 12:30 ` breaking DT compatibility (was: Re: [PATCH v4] clk: sunxi: Refactor A31 PLL6 so that it can be reused) Andre Przywara
2016-02-10 13:42 ` Rob Herring
2016-02-10 14:37 ` Maxime Ripard
2016-02-10 14:45 ` Arnd Bergmann
2016-02-10 16:14 ` breaking DT compatibility Andre Przywara
2016-02-11 10:16 ` Maxime Ripard
2016-02-10 16:30 ` breaking DT compatibility (was: Re: [PATCH v4] clk: sunxi: Refactor A31 PLL6 so that it can be reused) Mark Rutland
2016-02-11 10:00 ` Maxime Ripard
2016-02-11 11:44 ` Mark Rutland
2016-02-11 12:29 ` breaking DT compatibility Andre Przywara
2016-02-11 17:08 ` breaking DT compatibility (was: Re: [PATCH v4] clk: sunxi: Refactor A31 PLL6 so that it can be reused) Maxime Ripard
2016-02-12 9:40 ` Lucas Stach
2016-02-16 8:44 ` Maxime Ripard
2016-02-16 19:40 ` Michael Turquette
2016-02-11 14:51 ` Richard Cochran
2016-02-11 15:16 ` breaking DT compatibility Andre Przywara
2016-02-11 21:46 ` breaking DT compatibility (was: Re: [PATCH v4] clk: sunxi: Refactor A31 PLL6 so that it can be reused) Rob Herring
2016-02-10 12:59 ` [PATCH v4] clk: sunxi: Refactor A31 PLL6 so that it can be reused Maxime Ripard
2016-02-10 14:02 ` Rob Herring
2016-02-11 9:41 ` Maxime Ripard
2016-02-10 18:41 ` Mark Rutland
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=20160204120507.GC4270@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=hdegoede@redhat.com \
--cc=jenskuske@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=moinejf@free.fr \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=vishnupatekar0510@gmail.com \
--cc=wens@csie.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).