public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: Gregory CLEMENT <gregory.clement@free-electrons.com>
Cc: Mike Turquette <mturquette@linaro.org>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Lior Amsalem <alior@marvell.com>,
	Tawfik Bayouk <tawfik@marvell.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Nadav Haklai <nadavh@marvell.com>,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	linux-arm-kernel@lists.infradead.org,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 0/6] Marvell Armada 375 and 38x clocks drivers
Date: Sun, 16 Feb 2014 21:20:22 -0500	[thread overview]
Message-ID: <20140217022022.GF7862@titan.lakedaemon.net> (raw)
In-Reply-To: <1392053569-28037-1-git-send-email-gregory.clement@free-electrons.com>

On Mon, Feb 10, 2014 at 06:32:43PM +0100, Gregory CLEMENT wrote:
> Hi Mike,
> 
> Here are patches that add the clocks drivers for two new Marvell ARM
> SOCs that belong to the mach-mvebu family: the Armada 375 and the
> Armada 380/385. They are based on Cortex-A9 CPU cores, and share a
> number of peripherals with their predecessors in the mach-mvebu
> family.
> 
> The drivers added are similar to the one already used for the other
> SoCs of this family, as usual only the data are different the logic
> remains the same ans allow us to use the common part.
> 
> The core support (arch/arm/mach-mvebu) for these SOCs have just been
> posted, and we're aiming at having this merged for 3.15 if possible.
> 
> Thanks,
> 
> Gregory
> 
> Gregory CLEMENT (4):
>   clk: mvebu: add clock support for Armada 375
>   dt: Update binding information for mvebu core clocks with Armada 375
>   dt: Update binding information for mvebu gating clocks with Armada 375
>   clk: mvebu: add clock support for Armada 380/385
> 
> Thomas Petazzoni (2):
>   dt: Update binding information for mvebu core clocks with Armada
>     380/385
>   dt: Update binding information for mvebu gating clocks with Armada
>     380/385
> 
>  .../devicetree/bindings/clock/mvebu-core-clock.txt |  14 ++
>  .../bindings/clock/mvebu-gated-clock.txt           |  65 +++++++-
>  drivers/clk/mvebu/Kconfig                          |   8 +
>  drivers/clk/mvebu/Makefile                         |   2 +
>  drivers/clk/mvebu/armada-375.c                     | 184 +++++++++++++++++++++
>  drivers/clk/mvebu/armada-38x.c                     | 167 +++++++++++++++++++
>  6 files changed, 436 insertions(+), 4 deletions(-)
>  create mode 100644 drivers/clk/mvebu/armada-375.c
>  create mode 100644 drivers/clk/mvebu/armada-38x.c

Hey guys,

I've tentatively applied this series to mvebu/clk-3xx.  I can't build
test it until I pull in the core support.  So I'll keep it separate from
the regular clock driver changes just in case.

thx,

Jason.

      parent reply	other threads:[~2014-02-17  2:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 17:32 [PATCH 0/6] Marvell Armada 375 and 38x clocks drivers Gregory CLEMENT
2014-02-10 17:32 ` [PATCH 1/6] clk: mvebu: add clock support for Armada 375 Gregory CLEMENT
2014-02-10 17:32 ` [PATCH 2/6] dt: Update binding information for mvebu core clocks with " Gregory CLEMENT
2014-02-10 17:32 ` [PATCH 3/6] dt: Update binding information for mvebu gating " Gregory CLEMENT
2014-02-10 17:32 ` [PATCH 4/6] clk: mvebu: add clock support for Armada 380/385 Gregory CLEMENT
2014-02-10 17:32 ` [PATCH 5/6] dt: Update binding information for mvebu core clocks with " Gregory CLEMENT
2014-02-10 17:32 ` [PATCH 6/6] dt: Update binding information for mvebu gating " Gregory CLEMENT
2014-02-10 17:53   ` Andrew Lunn
2014-02-10 17:59     ` Thomas Petazzoni
2014-02-11 19:06       ` Jason Cooper
2014-02-17  2:20 ` Jason Cooper [this message]

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=20140217022022.GF7862@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=alior@marvell.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=nadavh@marvell.com \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=tawfik@marvell.com \
    --cc=thomas.petazzoni@free-electrons.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