From: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
To: "moderated list:ARM/S5P EXYNOS AR..."
<linux-samsung-soc@vger.kernel.org>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>
Subject: PM / devfreq: exynos-bus: need for suspend OPP?
Date: Mon, 21 Nov 2016 14:33:06 +0100 [thread overview]
Message-ID: <5832F792.4010308@math.uni-bielefeld.de> (raw)
Hello everyone,
I was thinking about the following. At the moment we have a suspend OPP
for cpufreq-dt in place for the Exynos4412 SoC (added in
1605b60ad064c7019db8ade07f0b7bdc8c197b93). The rationale behind is that
the board using the SoC might not have some PMIC reset in place. In case
the board goes into reboot with a low OPP (i.e. low frequency, but also
low core voltage), this results in a hang when the first-stage
bootloaders sets its default core frequency.
So this is properly handled in the kernel just fine, except for some
corner cases like emergency reboot.
But some time ago devfreq support for the various busses in the
Exynos4412 was added. On the ODROID boards e.g. this adjust MIF and INT
voltage.
Let us take the DMC bus. Operating frequency is 100~400MHz and voltage
is 900~1050mV.
Now let's look at the corresponding board file
(http://git.denx.de/?p=u-boot.git;a=blob;f=board/samsung/odroid/odroid.c#l234)
in upstream u-boot. If I read this correctly DMC is set to 400MHz there.
Here's the question. Could this, similar to the cpufreq/core frequency
issue, pose a problem when the kernel goes into reboot when DMC is on
the lowest OPP state?
I'm not saying that it does. This just came to my mind during some
recent discussion.
With best wishes,
Tobias
next reply other threads:[~2016-11-21 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 13:33 Tobias Jakobi [this message]
2016-11-21 14:48 ` PM / devfreq: exynos-bus: need for suspend OPP? Markus Reichl
2016-11-21 15:06 ` MyungJoo Ham
2016-11-21 15:23 ` Tobias Jakobi
2016-11-21 16:21 ` MyungJoo Ham
2016-11-21 22:15 ` Tobias Jakobi
2016-11-22 12:39 ` MyungJoo Ham
2016-11-23 13:55 ` Tobias Jakobi
2016-11-21 15:16 ` Tobias Jakobi
2016-11-21 18:10 ` Markus Reichl
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=5832F792.4010308@math.uni-bielefeld.de \
--to=tjakobi@math.uni-bielefeld.de \
--cc=cw00.choi@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.