From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-clk@vger.kernel.org, Nadav Haklai <nadavh@marvell.com>,
Lior Amsalem <alior@marvell.com>,
Jason Cooper <jason@lakedaemon.net>,
Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Yehuda Yitschak <yehuday@marvell.com>,
Neta Zur Hershkovits <neta@marvell.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH v3 0/3] clk: clock driver for the Marvell Armada AP806
Date: Tue, 08 Mar 2016 09:57:47 +0100 [thread overview]
Message-ID: <87r3fl4a9g.fsf@free-electrons.com> (raw)
In-Reply-To: <1457096275-7581-1-git-send-email-thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Fri, 4 Mar 2016 13:57:52 +0100")
Hi Thomas,
On ven., mars 04 2016, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Michael, Stephen,
>
> Here is a new version of the clock driver and its DT binding for the
> Marvell Armada AP806. As you will see, there is no longer any
> reference to the DFX Server and changes in the clock tree compared to
> the v2. This is due to the fact that the HW has changed from this
> point of view between the test chips and the final revision, and this
> new version aims at supporting only the final revision.
>
> We therefore have a very simple DT binding, with one single node that
> covers the entire "system controller" registers, associated to one
> driver that provides the clocks. This system controller will later be
> used to support other features such as pin-muxing, but for now we only
> support the clocks aspects of it.
>
> Please let me know if this approach works for you.
>
> Note that this patch series is based on clk-net, because I wanted to
> avoid introducing a new use of CLK_IS_ROOT. To do this, I needed the
> patches currently in clk-next that remove the need for CLK_IS_ROOT.
>
> Thanks!
The series is clean and small, I didn't see any problem with it, so for
the whole series:
Acked-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
Thanks,
Gregory
>
> Thomas
>
> Thomas Petazzoni (3):
> dt-bindings: arm: add DT binding for Marvell AP806 system controller
> clk: unconditionally recurse into clk/mvebu/
> clk: mvebu: new driver for Armada AP806 system controller
>
> .../arm/marvell/ap806-system-controller.txt | 34 +++++++
> drivers/clk/Makefile | 2 +-
> drivers/clk/mvebu/Kconfig | 3 +
> drivers/clk/mvebu/Makefile | 1 +
> drivers/clk/mvebu/ap806-system-controller.c | 106 +++++++++++++++++++++
> 5 files changed, 145 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/arm/marvell/ap806-system-controller.txt
> create mode 100644 drivers/clk/mvebu/ap806-system-controller.c
>
> --
> 2.6.4
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2016-03-08 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 12:57 [PATCH v3 0/3] clk: clock driver for the Marvell Armada AP806 Thomas Petazzoni
2016-03-04 12:57 ` [PATCH v3 1/3] dt-bindings: arm: add DT binding for Marvell AP806 system controller Thomas Petazzoni
2016-03-05 4:31 ` Rob Herring
2016-03-04 12:57 ` [PATCH v3 2/3] clk: unconditionally recurse into clk/mvebu/ Thomas Petazzoni
2016-03-04 12:57 ` [PATCH v3 3/3] clk: mvebu: new driver for Armada AP806 system controller Thomas Petazzoni
2016-03-08 8:57 ` Gregory CLEMENT [this message]
2016-03-16 13:16 ` [PATCH v3 0/3] clk: clock driver for the Marvell Armada AP806 Thomas Petazzoni
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=87r3fl4a9g.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=nadavh@marvell.com \
--cc=neta@marvell.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=yehuday@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox