Re: [PATCH v2 00/10] Marvell Berlin full clock support

From: Mike Turquette
Date: Wed May 28 2014 - 20:07:25 EST


Quoting Sebastian Hesselbarth (2014-05-19 09:43:21)
> Mike,
>
> this is v2 of the Berlin SoC clock driver [1] but with a reworked DT
> binding as requested [2]. We decided to not even try to split up the chip
> control registers that deal with pinmux, padmux, clock, reset, and evil
> stuff we haven't even looked at. Instead we keep a single node that clock
> driver will remap early, while proper platform_drivers use a regmap
> instead. Although clock and other drivers share the same register range,
> they use individual registers exclusively.
>
> There are some functional fixes in the single clock drivers, I noticed
> while retesting each individial driver. There will be more to fixup but
> without any drivers actually using the clocks, it is hard to tell what
> isn't working now.
>
> Anyway, the current binding should match what you requested and having
> a clock driver for v3.16 will really be a huge benefit for us to work
> on more driver support.
>
> If you are fine with it, please take patches 2-7 and I'll pick up
> 1,8-10 in berlin branch.

Patches #2-7 applied to clk-next.

Thanks!
Mike

>
> Sebastian
>
> [1] https://lkml.kernel.org/r/1399839881-29895-1-git-send-email-sebastian.hesselbarth@xxxxxxxxx
> [2] https://lkml.kernel.org/r/20140515044106.19795.57249@quantum
>
> Alexandre Belloni (4):
> clk: berlin: add driver for BG2x simple PLLs
> clk: berlin: add driver for BG2x complex divider cells
> clk: berlin: add core clock driver for BG2Q
> ARM: dts: berlin: convert BG2Q to DT clock nodes
>
> Sebastian Hesselbarth (6):
> dt-binding: ARM: add clock binding docs for Marvell Berlin2 SoCs
> clk: berlin: add binding include for Berlin SoC clock ids
> clk: berlin: add driver for BG2x audio/video PLL
> clk: berlin: add core clock driver for BG2/BG2CD
> ARM: dts: berlin: convert BG2CD to DT clock nodes
> ARM: dts: berlin: convert BG2 to DT clock nodes
>
> .../devicetree/bindings/arm/marvell,berlin.txt | 47 ++
> arch/arm/boot/dts/berlin2.dtsi | 56 +-
> arch/arm/boot/dts/berlin2cd.dtsi | 53 +-
> arch/arm/boot/dts/berlin2q.dtsi | 54 +-
> drivers/clk/Makefile | 1 +
> drivers/clk/berlin/Makefile | 4 +
> drivers/clk/berlin/berlin2-avpll.c | 393 ++++++++++++
> drivers/clk/berlin/berlin2-avpll.h | 36 ++
> drivers/clk/berlin/berlin2-div.c | 265 ++++++++
> drivers/clk/berlin/berlin2-div.h | 89 +++
> drivers/clk/berlin/berlin2-pll.c | 117 ++++
> drivers/clk/berlin/berlin2-pll.h | 37 ++
> drivers/clk/berlin/bg2.c | 691 +++++++++++++++++++++
> drivers/clk/berlin/bg2q.c | 389 ++++++++++++
> drivers/clk/berlin/common.h | 29 +
> include/dt-bindings/clock/berlin2.h | 45 ++
> include/dt-bindings/clock/berlin2q.h | 31 +
> 17 files changed, 2240 insertions(+), 97 deletions(-)
> create mode 100644 drivers/clk/berlin/Makefile
> create mode 100644 drivers/clk/berlin/berlin2-avpll.c
> create mode 100644 drivers/clk/berlin/berlin2-avpll.h
> create mode 100644 drivers/clk/berlin/berlin2-div.c
> create mode 100644 drivers/clk/berlin/berlin2-div.h
> create mode 100644 drivers/clk/berlin/berlin2-pll.c
> create mode 100644 drivers/clk/berlin/berlin2-pll.h
> create mode 100644 drivers/clk/berlin/bg2.c
> create mode 100644 drivers/clk/berlin/bg2q.c
> create mode 100644 drivers/clk/berlin/common.h
> create mode 100644 include/dt-bindings/clock/berlin2.h
> create mode 100644 include/dt-bindings/clock/berlin2q.h
>
> ---
> Cc: Rob Herring <robh+dt@xxxxxxxxxx>
> Cc: Pawel Moll <pawel.moll@xxxxxxx>
> Cc: Mark Rutland <mark.rutland@xxxxxxx>
> Cc: Ian Campbell <ijc+devicetree@xxxxxxxxxxxxxx>
> Cc: Kumar Gala <galak@xxxxxxxxxxxxxx>
> Cc: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
> Cc: Mike Turquette <mturquette@xxxxxxxxxx>
> Cc: Alexandre Belloni <alexandre.belloni@xxxxxxxxxxxxxxxxxx>
> Cc: Jisheng Zhang <jszhang@xxxxxxxxxxx>
> Cc: devicetree@xxxxxxxxxxxxxxx
> Cc: linux-doc@xxxxxxxxxxxxxxx
> Cc: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
> Cc: linux-kernel@xxxxxxxxxxxxxxx
> --
> 1.9.1
>
--
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/