Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752778AbbG3Mgy (ORCPT ); Thu, 30 Jul 2015 08:36:54 -0400 Received: from down.free-electrons.com ([37.187.137.238]:36014 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751315AbbG3Mfz (ORCPT ); Thu, 30 Jul 2015 08:35:55 -0400 From: Antoine Tenart To: sebastian.hesselbarth@gmail.com, mturquette@baylibre.com, sboyd@codeaurora.org Cc: Antoine Tenart , zmxu@marvell.com, jszhang@marvell.com, linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/3] ARM: berlin: add cpufreq support for the BG2Q Date: Thu, 30 Jul 2015 14:35:49 +0200 Message-Id: <1438259752-16320-1-git-send-email-antoine.tenart@free-electrons.com> X-Mailer: git-send-email 2.5.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1179 Lines: 38 Hi, This series adds the cpufreq support to the Berlin BG2Q SoC only, as I told this couldn't be done for BG2 and BG2CD. First, the cpuclk clock is added to the Berlin 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, when using a BG2Q. I also added the OPP table definition in the BG2Q device tree. Some bootloaders may update this table when booting. Mine doesn't. Tested on a BG2Q DMP. Thanks, Antoine Antoine Tenart (3): clk: berlin: add cpuclk ARM: berlin: register cpufreq-dt for the BG2Q ARM: berlin: dts: add the cpufreq-dt bindings on the BG2Q arch/arm/boot/dts/berlin2q.dtsi | 11 +++++++++++ arch/arm/mach-berlin/berlin.c | 13 +++++++++++++ drivers/clk/berlin/bg2q.c | 14 +++++++------- include/dt-bindings/clock/berlin2q.h | 3 ++- 4 files changed, 33 insertions(+), 8 deletions(-) -- 2.5.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/