Messages in this thread |  | | From | Stephen Boyd <> | Subject | Re: [PATCH 1/2] clk: qcom: gcc-msm8996: Fix parent for CLKREF clocks | Date | Thu, 26 Dec 2019 14:34:04 -0800 |
| |
Quoting Bjorn Andersson (2019-12-26 14:23:15) > On Mon 23 Dec 18:48 PST 2019, Stephen Boyd wrote: > > > Quoting Bjorn Andersson (2019-12-07 12:36:02) > > > The CLKREF clocks are all fed by the clock signal on the CXO2 pad on the > > > SoC. Update the definition of these clocks to allow this to be wired up > > > to the appropriate clock source. > > > > > > Retain "xo" as the global named parent to make the change a nop in the > > > event that DT doesn't carry the necessary clocks definition. > > > > > > Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> > > > --- > > > .../devicetree/bindings/clock/qcom,gcc.yaml | 6 ++-- > > > drivers/clk/qcom/gcc-msm8996.c | 35 +++++++++++++++---- > > > 2 files changed, 32 insertions(+), 9 deletions(-) > > > > What is this patch based on? I think I'm missing some sort of 8996 yaml > > gcc binding patch. > > > > The patch applies cleanly on linux-next and afaict it depends on the > yamlification done in 9de7269e9703 ("dt-bindings: clock: Add YAML > schemas for the QCOM GCC clock bindings"), which git tells me is > included in v5.5-rc1 as well. > > Am I misunderstanding your question? >
There doesn't seem to be any sort of minitems or maxitems in my yaml binding file for the clocks or clock-names properties.
|  |