On 1/13/2017 12:09 AM, Bjorn Andersson wrote:
On Thu 12 Jan 05:53 PST 2017, Avaneesh Kumar Dwivedi wrote:
This document defines the binding for a component that loads firmware
and control the life cycle of the Qualcomm slpi core.
Rather than duplicating the adsp binding I think we should just amend
the adsp binding - and probably rename the file.
Yes, missed to amend the mention of adsp core, some places.
diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,slpi.txt b/Documentation/devicetree/bindings/remoteproc/qcom,slpi.txt
[..]
+= EXAMPLE
[..]
+ clocks = <&rpmcc MSM8996_RPM_SMD_XO_CLK_SRC>,
+ <&rpmcc MSM8996_RPM_SMD_AGGR2_NOC_CLK>;
+ clock-names = "xo",
+ "aggre2";
+
I still haven't managed to acquire the block diagram for this chip and
we have ongoing msm_bus discussions, but I believe we want something
representing a bus to control this clock.
Do you mean any "NOC clock" need to be separately turned on by a bus
driver not by the device driver itself?
Regards,
Bjorn
--
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
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
--
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
