[v9] * clean up recalc function to use integer division. * Add back type casting the desc data passed to "getter" function and added comment for the same. [v8] * cleanup code to remove of rpmh_client handle. * pass the hw_clks array to the devm_of_clk_add_hw_provider getter function. [v7] * Addressed comments from Stephen - Keep only xo_board as clock parent. - Associate divs from SoC specific clock listing to calculate the clock rate. - Add back the recalc_rate clock ops to return the clock rate based on the parent rate and div associated with clock. - void cast kept to avoid compiler warnings. [v6] * Addressed comments from Rob * Addressed comments from Stephen [v5] * Addressed comments from Stephen * Introduced a new DT property to take clock divs [v4] * Addressed comments from Stephen [v3] * Addressed documentation & code review comments from Bjorn * Addressed bindings comments from Rob * Updated the patch series order for bindings [v2] * Addressed comments from Stephen * Addressed comments from Evan This patch series adds a driver and device tree documentation binding for the clock control via Resource Power Manager-hardened (RPMh) on some Qualcomm Technologies, Inc, SoCs such as SDM845. The clock RPMh driver would send requests for the RPMh managed clock resources. The RPMh clock driver depends upon the RPMh driver [1] and command DB driver [2] which are both still undergoing review. Thanks, Taniya [1]: https://lkml.org/lkml/2018/3/9/979 [2]: https://lkml.org/lkml/2018/3/14/787 Taniya Das (1): clk: qcom: clk-rpmh: Add QCOM RPMh clock driver drivers/clk/qcom/Kconfig | 9 ++ drivers/clk/qcom/Makefile | 1 + drivers/clk/qcom/clk-rpmh.c | 333 ++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 343 insertions(+) create mode 100644 drivers/clk/qcom/clk-rpmh.c -- Qualcomm INDIA, on behalf of Qualcomm Innovation Center, Inc.is a member of the Code Aurora Forum, hosted by the Linux Foundation. -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
