On 03/22, Rajendra Nayak wrote: > This patchset adds all the RPM clocks on msm8996 platforms, > while at it, we also remove some of the RCGs from the GCC > driver as they are controlled by RPM and hence should not > be part of GCC. > > Series depends on Bjorns patches which add support for glink > on msm8996 > https://www.spinics.net/lists/linux-wireless/msg160393.html > http://www.spinics.net/lists/devicetree/msg168445.html > > Rajendra Nayak (2): > clk: qcom: clk-smd-rpm: add msm8996 rpmclks > clk: qcom: gcc-msm8996: Remove RPM controlled clocks The first patch looks ok, but the second patch is quite scary. So far we haven't hooked up the bus RPM clks into the clk tree quite like that. I suppose if everything works fine though it should be OK. One case I can think of is when we're enabling branch clks that are children of some RPM controlled bus clk. Right now in the downstream kernel we don't enable the RPM clk in this case. Instead, we rely on the bus driver to make sure the bus is enabled. And for things like suspend, I'm not sure if drivers are calling clk_disable() and unprepare on their branches, so we may be leaving them on in the downstream kernel and relying on the bus driver dropping requests to explicitly turn things off. I suppose this is OK though, because those drivers are broken if they exist. Also, probe deferal may be an issue, where we hand out branch clks to drivers before the RPM is up and ready. If an enable appears on an orphan things get confusing. We should merge that probe defer orphan series too. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
