From: Oliver Graute <oliver.graute@gmail.com>
To: aisheng.dong@nxp.com, anson.huang@nxp.com
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
linux-imx@nxp.com, leonard.crestez@nxp.com, festevam@gmail.com,
s.hauer@pengutronix.de, linux-arm-kernel@lists.infradead.org
Subject: Re: RFC: imx8qm: imx-scu-clk: probe of clk failed
Date: Thu, 27 Feb 2020 16:31:10 +0100 [thread overview]
Message-ID: <20200227153110.GD16310@optiplex> (raw)
In-Reply-To: <20200227125743.GC16310@optiplex>
On 27/02/20, Oliver Graute wrote:
> Hello Aisheng,
> Hello Anson,
>
> I get the following imx-scu errors when using Linux version
> 5.6.0-rc1-next-20200214 with scfw Build 3353, Commit 494c97f3
>
> It seems that important clocks are off somehow and that lpspi isn't
> working because of that. What is the best way to debug such issues?
>
> [ 1.103799] imx-scu scu: NXP i.MX SCU Initialized
> [ 1.111383] a35_clk: failed to get clock rate -22
After some deeper digging I saw that the reason for "a35_clk: failed" is
an IMX_SC_ERR_PARM = 3. Because he trys to get the resource SC_R_A35
which is only available on imx8qxp and not on imx8qm. No clue why he try
that instead of SC_R_A53.
Best regards,
Oliver
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-27 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 12:57 RFC: imx8qm: imx-scu-clk: probe of clk failed Oliver Graute
2020-02-27 15:31 ` Oliver Graute [this message]
2020-02-28 0:40 ` Anson Huang
2020-02-28 9:14 ` Oliver Graute
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=20200227153110.GD16310@optiplex \
--to=oliver.graute@gmail.com \
--cc=aisheng.dong@nxp.com \
--cc=anson.huang@nxp.com \
--cc=festevam@gmail.com \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=mturquette@baylibre.com \
--cc=s.hauer@pengutronix.de \
/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).