[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1442484905-15656-1-git-send-email-antoine.tenart@free-electrons.com>
Date: Thu, 17 Sep 2015 12:14:59 +0200
From: Antoine Tenart <antoine.tenart@...e-electrons.com>
To: sebastian.hesselbarth@...il.com
Cc: Antoine Tenart <antoine.tenart@...e-electrons.com>,
zmxu@...vell.com, jszhang@...vell.com,
linux-arm-kernel@...ts.infradead.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH v3 0/6] ARM: berlin: add cpufreq support
Hi,
This series adds the cpufreq support to the Berlin SoCs, using
cpufreq-dt.
First, the cpuclk clock is added to the BG2Q clock driver. This clock
has a divider fixed to 1, so we use a fixed factor clock here.
Then register a platform device for cpufreq-dt.
I also added the OPP table definition in the BG2Q, BG2 and BG2CD device
trees. When using a BG2Q, some bootloaders may update this table when
booting (mine doesn't).
Tested on a BG2Q DMP.
Thanks,
Antoine
Changes since v2:
- rebased on top of v4.3-rc1
Changes since v1:
- added the BG2 and BG2CD support
- moved MAX_CLKS out of the Berlin clk driver
- reordered the patches
Antoine Tenart (6):
clk: berlin: move MAX_CLKS out of drivers/clk/berlin
clk: berlin: add cpuclk
ARM: berlin: dts: add the cpufreq-dt bindings on the BG2Q
ARM: berlin: dts: add the cpufreq-dt bindings on the BG2
ARM: berlin: dts: add the cpufreq-dt bindings on the BG2CD
ARM: berlin: register cpufreq-dt
arch/arm/boot/dts/berlin2.dtsi | 10 ++++++++++
arch/arm/boot/dts/berlin2cd.dtsi | 8 ++++++++
arch/arm/boot/dts/berlin2q.dtsi | 11 +++++++++++
arch/arm/mach-berlin/berlin.c | 6 ++++++
drivers/clk/berlin/bg2.c | 1 -
drivers/clk/berlin/bg2q.c | 13 ++++++-------
include/dt-bindings/clock/berlin2.h | 2 ++
include/dt-bindings/clock/berlin2q.h | 3 +++
8 files changed, 46 insertions(+), 8 deletions(-)
--
2.5.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists