linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Jeffrey Hugo <jhugo@codeaurora.org>
Cc: Marc Gonzalez <marc.w.gonzalez@free.fr>,
	Stephen Boyd <sboyd@kernel.org>,
	MSM <linux-arm-msm@vger.kernel.org>,
	Andy Gross <andy.gross@linaro.org>,
	Georgi Djakov <georgi.djakov@linaro.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/3] arm64: dts: qcom: msm8998: correct xo clock name
Date: Wed, 5 Dec 2018 08:48:43 -0800	[thread overview]
Message-ID: <20181205164843.GB1492@tuxbook-pro> (raw)
In-Reply-To: <0ba54ffd-1d47-5ae9-ae9c-4a03d57e6ff3@codeaurora.org>

On Wed 05 Dec 08:38 PST 2018, Jeffrey Hugo wrote:

> On 12/5/2018 9:12 AM, Marc Gonzalez wrote:
> > On 15/11/2018 21:44, Jeffrey Hugo wrote:
> > 
> > > The root parent clock of most msm8998 clock is the "xo" clock.  The DT node
> > > is incorrectly named "xo_board", which prevents Linux from correctly
> > > parsing the clock tree, resulting in most clocks being unparented and
> > > unable to be manipulated.  The end result is that we can't turn on clocks
> > > for peripherals like SD, so init usually fails.
> > > 
> > > Fixes: 4807c71cc688 (arm64: dts: Add msm8998 SoC and MTP board support)
> > > Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> > > Signed-off-by: Jeffrey Hugo <jhugo@codeaurora.org>
> > > ---
> > >   arch/arm64/boot/dts/qcom/msm8998.dtsi | 2 +-
> > >   1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/arch/arm64/boot/dts/qcom/msm8998.dtsi b/arch/arm64/boot/dts/qcom/msm8998.dtsi
> > > index 78227cc..a948d4b 100644
> > > --- a/arch/arm64/boot/dts/qcom/msm8998.dtsi
> > > +++ b/arch/arm64/boot/dts/qcom/msm8998.dtsi
> > > @@ -53,7 +53,7 @@
> > >   	};
> > >   	clocks {
> > > -		xo_board {
> > > +		xo {
> > >   			compatible = "fixed-clock";
> > >   			#clock-cells = <0>;
> > >   			clock-frequency = <19200000>;
> > > 
> > 
> > Isn't there going to be a problem for msm8998 in drivers/clk/qcom/clk-smd-rpm.c
> > which uses "xo_board" for parent_names?
> 
> Looks like you are right.  This doesn't seem to be the correct way to
> address the issue then.  I'll have to dig in and take another look.
> 

The appropriate solution is to describe references between clock drivers
explicitly in DeviceTree and by that not rely on a global namespace.
That will also sort out any initialization ordering issues that we might
have.

But this task has not yet made it off the todo lists where it lives...

Regards,
Bjorn

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2018-12-05 16:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1542314695-24071-1-git-send-email-jhugo@codeaurora.org>
     [not found] ` <1542314695-24071-2-git-send-email-jhugo@codeaurora.org>
2018-12-05 16:12   ` [PATCH v2 1/3] arm64: dts: qcom: msm8998: correct xo clock name Marc Gonzalez
2018-12-05 16:38     ` Jeffrey Hugo
2018-12-05 16:48       ` Bjorn Andersson [this message]
2018-12-05 17:03         ` Jeffrey Hugo
2018-12-05 21:04           ` Stephen Boyd
2018-12-05 21:20             ` Jeffrey Hugo
2018-12-05 21:42               ` Stephen Boyd
2018-12-05 23:04                 ` Jeffrey Hugo
2018-12-06 18:34                   ` Stephen Boyd
2018-12-07  9:03                     ` Marc Gonzalez
2018-12-07 14:58                       ` Jeffrey Hugo
2018-12-07 18:23                         ` Andy Gross

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=20181205164843.GB1492@tuxbook-pro \
    --to=bjorn.andersson@linaro.org \
    --cc=andy.gross@linaro.org \
    --cc=georgi.djakov@linaro.org \
    --cc=jhugo@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=marc.w.gonzalez@free.fr \
    --cc=sboyd@kernel.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).