mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-21 08:46:49 +07:00
922b8fae08
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". That's all well and good.
...but the example in the bindings shows this clock mapping to the
clock "xo_board". On the current sdm845.dtsi file the "xo_board"
clock is a fixed clock with an output name of "xo_board". The clock
with the name "bi_tcxo" is actually provided by the RPMh Clock
Controller. Presumably that's the one that was wanted.
Let's update the example to make this clearer.
Fixes: e431c92188 ("dt-bindings: clock: Introduce QCOM Graphics clock bindings")
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Signed-off-by: Stephen Boyd <sboyd@kernel.org>
23 lines
736 B
Plaintext
23 lines
736 B
Plaintext
Qualcomm Graphics Clock & Reset Controller Binding
|
|
--------------------------------------------------
|
|
|
|
Required properties :
|
|
- compatible : shall contain "qcom,sdm845-gpucc"
|
|
- reg : shall contain base register location and length
|
|
- #clock-cells : from common clock binding, shall contain 1
|
|
- #reset-cells : from common reset binding, shall contain 1
|
|
- #power-domain-cells : from generic power domain binding, shall contain 1
|
|
- clocks : shall contain the XO clock
|
|
- clock-names : shall be "xo"
|
|
|
|
Example:
|
|
gpucc: clock-controller@5090000 {
|
|
compatible = "qcom,sdm845-gpucc";
|
|
reg = <0x5090000 0x9000>;
|
|
#clock-cells = <1>;
|
|
#reset-cells = <1>;
|
|
#power-domain-cells = <1>;
|
|
clocks = <&rpmhcc RPMH_CXO_CLK>;
|
|
clock-names = "xo";
|
|
};
|