From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: linux-clk@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
NXP Linux Team <linux-imx@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: sdhci-esdhc-imx/v5.0-rc5: i.MX50 system hangs when "per" clock is disabled
Date: Sun, 10 Feb 2019 22:32:21 +0100 [thread overview]
Message-ID: <20190210213221.GC2061@latitude> (raw)
In-Reply-To: <20190207225211.GA17552@latitude>
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
On Thu, Feb 07, 2019 at 11:52:11PM +0100, Jonathan Neuschäfer wrote:
> However, as soon as the mmc driver (sdhci-esdhc-imx.c) disables clk_per
> in sdhci_esdhc_runtime_suspend[2], the whole system locks up in some way.
I've traced clk prepare/unprepare/enable/disable calls and got this
right before it hangs:
[ 1.280981] sdhci_esdhc_runtime_suspend: unprepare clk_per
[ 1.283356] clk_core_unprepare esdhc1_per_gate
[ 1.285191] clk_core_unprepare esdhc_a_podf
[ 1.286881] clk_core_unprepare esdhc_a_pred
[ 1.288568] clk_core_unprepare esdhc_a_sel
[ 1.290220] clk_core_unprepare pll2_sw
I suspect that there is a dependency on pll2_sw that is not represented
in the imx5 clock driver. I'm comparing it to the Reference Manual now.
Thanks,
Jonathan Neuschäfer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-02-10 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 22:52 sdhci-esdhc-imx/v5.0-rc5: i.MX50 system hangs when "per" clock is disabled Jonathan Neuschäfer
2019-02-08 0:50 ` Fabio Estevam
2019-02-09 16:24 ` Jonathan Neuschäfer
2019-02-09 17:15 ` Fabio Estevam
2019-02-10 21:32 ` Jonathan Neuschäfer [this message]
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=20190210213221.GC2061@latitude \
--to=j.neuschaefer@gmx.net \
--cc=adrian.hunter@intel.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@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).