On Fri 20 Nov 16:39 PST 2015, Stephen Boyd wrote: > On 11/19, Georgi Djakov wrote: > > diff --git a/Documentation/devicetree/bindings/clock/qcom,rpmcc.txt b/Documentation/devicetree/bindings/clock/qcom,rpmcc.txt > > new file mode 100644 > > index 000000000000..bd0fd0cd50dc > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/clock/qcom,rpmcc.txt > > @@ -0,0 +1,35 @@ > > +Qualcomm RPM Clock Controller Binding > > +------------------------------------------------ > > +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. > > + > > +Required properties : > > +- compatible : shall contain only one of the following: > > + > > + "qcom,rpmcc-msm8916" > > We need to add qcom,rpmcc as a generic compatible as well. > The binding is generic and the clock defines global, so this should work fine on the dt side of things. But how do we implement this? Which set of clocks does the generic rpmcc actually provide? Do you foresee that there will be an implementation of the generic rpmcc or is it just a way to "standardize" the dt binding? 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
