From: Vincent Knecht <vincent.knecht@mailoo.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Bryan O'Donoghue <pure.logic@nexus-software.ie>,
agross@kernel.org, bjorn.andersson@linaro.org,
mturquette@baylibre.com, sboyd@kernel.org, robh+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
shawn.guo@linaro.org, p.zabel@pengutronix.de,
Konrad Dybcio <konradybcio@gmail.com>
Subject: Re: [PATCH v3 0/2] Add Qualcomm MSM8939 GCC binding and driver
Date: Fri, 08 May 2020 12:06:23 +0200 [thread overview]
Message-ID: <f9413ee5ca2fb0d85015f8b5988cbc61418e50f0.camel@mailoo.org> (raw)
In-Reply-To: <90cda746-2caa-cb79-9304-17a97886f1fc@linaro.org>
Le jeudi 07 mai 2020 à 17:06 +0100, Bryan O'Donoghue a écrit :
> On 07/05/2020 16:57, Bryan O'Donoghue wrote:
> > On 23/04/2020 11:34, Bryan O'Donoghue wrote:
> > > V3:
> > > This update removes the old clock name arrays which I forgot to prune in
> > > the previous V2.
> > >
> > > git diff bod/clk-next+msm8939 bod/clk-next+msm8939-v2.1
> >
> > I should have mentioned.
> >
> > If you want to test this you'll need to do the following to your
> > msm8939.dtsi
> >
> > diff --git a/arch/arm64/boot/dts/qcom/msm8939.dtsi
> > b/arch/arm64/boot/dts/qcom/msm8939.dtsi
> > index 996425a70014..2d54ad7f99b6 100644
> > --- a/arch/arm64/boot/dts/qcom/msm8939.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/msm8939.dtsi
> > @@ -673,6 +673,10 @@ gcc: clock-controller@1800000 {
> > reg = <0x1800000 0x80000>;
> > + clock-names = "xo",
> > + "sleep_clk";
> > + clocks = <&xo_board>,
> > + <&sleep_clk>;
> > };
> >
> > "xo" and "sleep_clk" names can be resolved.
> >
> > ---
> > bod
>
> and this...
>
> clocks {
> xo_board: xo_board {
> compatible = "fixed-clock";
> #clock-cells = <0>;
> clock-frequency = <19200000>;
> };
>
> sleep_clk: sleep_clk {
> compatible = "fixed-clock";
> #clock-cells = <0>;
> clock-frequency = <32768>;
> };
> };
>
Thank you, works for me over v5.7-rc2 with an Alcatel Idol 3 (5.5").
Tested-by: Vincent Knecht <vincent.knecht@mailoo.org>
next prev parent reply other threads:[~2020-05-08 10:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 10:34 [PATCH v3 0/2] Add Qualcomm MSM8939 GCC binding and driver Bryan O'Donoghue
2020-04-23 10:34 ` [PATCH v3 1/2] clk: qcom: Add DT bindings for MSM8939 GCC Bryan O'Donoghue
2020-05-11 20:32 ` Rob Herring
2020-05-07 15:57 ` [PATCH v3 0/2] Add Qualcomm MSM8939 GCC binding and driver Bryan O'Donoghue
2020-05-07 16:06 ` Bryan O'Donoghue
2020-05-08 10:06 ` Vincent Knecht [this message]
[not found] ` <20200423103406.481289-3-bryan.odonoghue@linaro.org>
2020-05-11 20:35 ` [PATCH v3 2/2] clk: qcom: gcc-msm8939: Add MSM8939 Generic Clock Controller Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f9413ee5ca2fb0d85015f8b5988cbc61418e50f0.camel@mailoo.org \
--to=vincent.knecht@mailoo.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=bryan.odonoghue@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=pure.logic@nexus-software.ie \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=shawn.guo@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).