[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191226222315.GD1908628@ripper>
Date: Thu, 26 Dec 2019 14:23:15 -0800
From: Bjorn Andersson <bjorn.andersson@...aro.org>
To: Stephen Boyd <sboyd@...nel.org>
Cc: Mark Rutland <mark.rutland@....com>,
Michael Turquette <mturquette@...libre.com>,
Rob Herring <robh+dt@...nel.org>,
Andy Gross <agross@...nel.org>, linux-arm-msm@...r.kernel.org,
linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Paolo Pisati <p.pisati@...il.com>
Subject: Re: [PATCH 1/2] clk: qcom: gcc-msm8996: Fix parent for CLKREF clocks
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@...aro.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?
Regards,
Bjorn
Powered by blists - more mailing lists