Quoting Stephen Boyd (2014-04-04 11:45:36)

+Example:
+       clock-controller@4000000 {
+               compatible = "qcom,mmcc-msm8974";
+               reg = <0x4000000 0x1000>;
+               #clock-cells = <1>;
+               #reset-cells = <1>;
+
+               regulators {
+                       gdsc_oxili_gx: gdsc_oxili_gx {
+                               regulator-name = "gdsc_oxili_gx";

Hi Stephen,

It makes sense to model the gdsc's as regulators. It also makes sense to
nest them within the clock-controller node, assuming that matches the
register manual for your part.

However, does it make sense to put this new code under drivers/clk/qcom?
I don't see a compelling reason. How about breaking the registers out
into a header for easier reuse?

Regards,
Mike

+                               parent-supply = <&pm8841_s4>;
+                               qcom,retain-mem;
+                               qcom,retain-periph;
+                               qcom,skip-logic-collapse;
+                               qcom,support-hw-trigger;
+                       };
+               };
+       };
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation