Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759879AbbLCODL (ORCPT ); Thu, 3 Dec 2015 09:03:11 -0500 Received: from mail-wm0-f44.google.com ([74.125.82.44]:33833 "EHLO mail-wm0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755560AbbLCODG (ORCPT ); Thu, 3 Dec 2015 09:03:06 -0500 From: Georgi Djakov To: sboyd@codeaurora.org, agross@codeaurora.org Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org, bjorn.andersson@sonymobile.com, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, georgi.djakov@linaro.org Subject: [PATCH v5 0/6] Add initial support for RPM clocks Date: Thu, 3 Dec 2015 16:02:50 +0200 Message-Id: <1449151376-25930-1-git-send-email-georgi.djakov@linaro.org> X-Mailer: git-send-email 1.7.9.5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3464 Lines: 76 This patchset adds initial support for the clocks controlled by the RPM (Resource Power Manager) processor on Qualcomm platforms. The RPM is a dedicated hardware engine for managing the shared SoC resources in order to keep the lowest power profile. It communicates with other hardware subsystems via shared memory and accepts clock requests, aggregates the requests and turns the clocks on/off or scales them on demand. Until now the RPM clock controller was not supported and a hard- coded fixed-rate clocks were registered in the drivers. Now we are moving the on-board clocks to the DT (where they actually belong). If the RPM clock controller is enabled we insert it right after the DT clocks making it a parent of some GCC clocks. The DT patches should go through the soc/qcom tree. This also depends on smem, smd and rpm drivers. Changes since v4 (https://lkml.org/lkml/2015/11/19/309) * Re-organize code into two separate drivers: - clk-smd-rpm for RPM over SMD based clocks like msm8916 - clk-rpm for RPM based clocks like apq8064 * Drop the patches that are already merged. * Added the extra compatible string to docs and example. Changes since v3 (https://lkml.org/lkml/2015/10/20/613) * Drop some of the patches as now we handle both scenarios - RPMCC enabled or disabled. * Addressed more comments from Stephen. Thanks again! Changes since v2 (https://lkml.org/lkml/2015/8/3/513) * Addressed various comments from Stephen. Thanks! * Added sleep sets support. * Added a mutex in the RPM driver. * Support both scenarios - RPMCC enabled or disabled. * Make RPMCC more generic in order to support other SMD RPM based platforms. Changes since v1 (https://lkml.org/lkml/2015/7/9/257): * Changed the driver name to clk-smd-rpm, also build it only when it is needed - suggested by Srini and Bjorn. * More detailed binding example. * Minor changes. Georgi Djakov (6): clk: qcom: Add support for SMD-RPM Clocks arm64: dts: qcom: msm8916: Add fixed rate on-board oscillators arm64: dts: qcom: msm8916: Add RPMCC DT node clk: qcom: Add support for RPM Clocks arm: dts: qcom: apq8064: Add fixed rate on-board oscillators arm: dts: qcom: apq8064: Add RPMCC DT node .../devicetree/bindings/clock/qcom,rpmcc.txt | 37 ++ arch/arm/boot/dts/qcom-apq8064.dtsi | 25 ++ arch/arm64/boot/dts/qcom/msm8916.dtsi | 20 + drivers/clk/qcom/Kconfig | 19 + drivers/clk/qcom/Makefile | 2 + drivers/clk/qcom/clk-rpm.c | 290 +++++++++++++ drivers/clk/qcom/clk-rpm.h | 71 ++++ drivers/clk/qcom/clk-smd-rpm.c | 433 ++++++++++++++++++++ drivers/clk/qcom/clk-smd-rpm.h | 142 +++++++ include/dt-bindings/clock/qcom,rpmcc.h | 45 ++ 10 files changed, 1084 insertions(+) create mode 100644 Documentation/devicetree/bindings/clock/qcom,rpmcc.txt create mode 100644 drivers/clk/qcom/clk-rpm.c create mode 100644 drivers/clk/qcom/clk-rpm.h create mode 100644 drivers/clk/qcom/clk-smd-rpm.c create mode 100644 drivers/clk/qcom/clk-smd-rpm.h create mode 100644 include/dt-bindings/clock/qcom,rpmcc.h -- 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/