On Sat, Mar 13, 2021 at 03:19:18AM +0100, Konrad Dybcio wrote: > Some devices come with a different SDCC clock configuration, > account for that. > > Signed-off-by: Konrad Dybcio <konrad.dybcio@xxxxxxxxxxxxxx> > --- > .../bindings/clock/qcom,gcc-msm8994.yaml | 4 ++++ > drivers/clk/qcom/gcc-msm8994.c | 16 ++++++++++++++++ > 2 files changed, 20 insertions(+) > > diff --git a/Documentation/devicetree/bindings/clock/qcom,gcc-msm8994.yaml b/Documentation/devicetree/bindings/clock/qcom,gcc-msm8994.yaml > index f8067fb1bbd6..9db0800a4ee4 100644 > --- a/Documentation/devicetree/bindings/clock/qcom,gcc-msm8994.yaml > +++ b/Documentation/devicetree/bindings/clock/qcom,gcc-msm8994.yaml > @@ -49,6 +49,10 @@ properties: > description: > Protected clock specifier list as per common clock binding. > > + qcom,sdcc2-clk-src-40mhz: > + description: SDCC2_APPS clock source runs at 40MHz. > + type: boolean Why don't you have some input clock you can get the rate from? > + > required: > - compatible > - reg
