Re: [PATCH 0/6] Marvell Armada 375 and 38x clocks drivers

From: Jason Cooper
Date: Sun Feb 16 2014 - 21:20:42 EST


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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/