Re: [PATCH 1/2] dt-bindings: clock: qcom: Fix the xo parent in gpucc example

Quoting Douglas Anderson (2018-11-28 10:57:42) > diff --git a/Documentation/devicetree/bindings/clock/qcom,gpucc.txt > b/Documentation/devicetree/bindings/clock/qcom,gpucc.txt > index 9d0358cc08b4..4e5215ef1acd 100644 > --- a/Documentation/devicetree/bindings/clock/qcom,gpucc.txt > +++

Re: [PATCH 1/2] dt-bindings: clock: qcom: Fix the xo parent in gpucc example

Quoting Douglas Anderson (2018-11-28 10:57:42) > diff --git a/Documentation/devicetree/bindings/clock/qcom,gpucc.txt > b/Documentation/devicetree/bindings/clock/qcom,gpucc.txt > index 9d0358cc08b4..4e5215ef1acd 100644 > --- a/Documentation/devicetree/bindings/clock/qcom,gpucc.txt > +++

[PATCH 1/2] dt-bindings: clock: qcom: Fix the xo parent in gpucc example

In the bindings that landed for the gpucc we require that the XO clock (one possible parent of the gpucc) be listed. The code doesn't use this yet--this is just to allow us to move toward the day when it does use it. What the code does do today is to hardcode the parent name to "bi_tcxo".

[PATCH 1/2] dt-bindings: clock: qcom: Fix the xo parent in gpucc example

In the bindings that landed for the gpucc we require that the XO clock (one possible parent of the gpucc) be listed. The code doesn't use this yet--this is just to allow us to move toward the day when it does use it. What the code does do today is to hardcode the parent name to "bi_tcxo".