From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Stephan Gerhold <stephan@gerhold.net>,
Ulf Hansson <ulf.hansson@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Stephen Boyd <sboyd@kernel.org>, Nishanth Menon <nm@ti.com>,
nks@flawful.org, Georgi Djakov <georgi.djakov@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Wolfram Sang <wsa@the-dreams.de>,
Linux I2C <linux-i2c@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH V2 2/2] cpufreq: dt: Refactor initialization to handle probe deferral properly
Date: Wed, 28 Oct 2020 10:49:45 +0100 [thread overview]
Message-ID: <CAMuHMdXnfG8riHYsd9PYSHTDvJ11zQ27y_JJh_9+obUxxLen0g@mail.gmail.com> (raw)
In-Reply-To: <20201028054829.42zckdtwvj67tcfl@vireshk-i7>
Hi Viresh,
On Wed, Oct 28, 2020 at 6:48 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
> On 27-10-20, 17:29, Geert Uytterhoeven wrote:
> > On plain v5.9, with #define DEBUG and a few extra debug prints
> > added, I get:
> >
> > cpufreq_dt: cpufreq_init:164: policy->cpu = 0
> > cpufreq_dt: cpufreq_init:165: policy->cpus = 0
> > cpufreq_dt: cpufreq_init:166: policy->related_cpus =
> > cpufreq_dt: cpufreq_init:167: policy->real_cpus =
> > cpu cpu0: dev_pm_opp_of_get_sharing_cpus: Couldn't find opp node.
> > of: dev_pm_opp_of_cpumask_add_table:1049
> > of: dev_pm_opp_of_cpumask_add_table:1054: cpu 0
> > cpu cpu0: dev_pm_opp_of_add_table:954
> > cpu cpu0: dev_pm_opp_of_add_table:956:
> > dev_pm_opp_get_opp_table_indexed() returned (ptrval)
> > cpu cpu0: _of_add_opp_table_v1:891
> > cpu cpu0: _of_add_opp_table_v1:893: _find_opp_table() returned (ptrval)
> > cpu cpu0: _of_add_opp_table_v1:909: 6 entries
> > cpu cpu0: dev_pm_opp_get_opp_count:331
> > cpu cpu0: dev_pm_opp_get_opp_count:333: _find_opp_table() returned (ptrval)
> > cpu cpu0: dev_pm_opp_get_opp_count:342: _get_opp_count() returned 6
> > cpu cpu0: dev_pm_opp_get_opp_count:331
> > cpu cpu0: dev_pm_opp_get_opp_count:333: _find_opp_table() returned (ptrval)
> > cpu cpu0: dev_pm_opp_get_opp_count:342: _get_opp_count() returned 6
> > cpu cpu0: dev_pm_opp_get_opp_count:331
> > cpu cpu0: dev_pm_opp_get_opp_count:333: _find_opp_table() returned (ptrval)
> > cpu cpu0: dev_pm_opp_get_opp_count:342: _get_opp_count() returned 6
> > cpu cpu0: Couldn't find proper 'dynamic-power-coefficient' in DT
> > cpu cpu0: Couldn't register Energy Model -22
> >
> > This happens quite late in the boot sequence, long after cpu1 has been
> > brought online.
> > So it finds the v1 opp table for cpu0, which has 6 entries.
> > The last two messages should be harmless, right?
>
> Yes.
>
> > So you say cpufreq is not working? How can I verify that?
>
> I said it because your earlier logs showed that we defered probed
> again or the count was 0 and we failed. Something like that.
>
> Give output of this to verify if cpufreq is working or not:
>
> grep . /sys/devices/system/cpu/cpufreq/policy*/*
>
> This will be empty if there is no cpufreq.
/sys/devices/system/cpu/cpufreq/policy0/affected_cpus:0 1
/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq:375000
/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq:1500000
/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_min_freq:375000
/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_transition_latency:300000
/sys/devices/system/cpu/cpufreq/policy0/related_cpus:0 1
/sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies:375000
750000 937500 1125000 1312500 1500000
/sys/devices/system/cpu/cpufreq/policy0/scaling_available_governors:conservative
ondemand userspace powersave performance schedutil
/sys/devices/system/cpu/cpufreq/policy0/scaling_cur_freq:375000
/sys/devices/system/cpu/cpufreq/policy0/scaling_driver:cpufreq-dt
/sys/devices/system/cpu/cpufreq/policy0/scaling_governor:schedutil
/sys/devices/system/cpu/cpufreq/policy0/scaling_max_freq:1500000
/sys/devices/system/cpu/cpufreq/policy0/scaling_min_freq:375000
/sys/devices/system/cpu/cpufreq/policy0/scaling_setspeed:<unsupported>
So it works in v5.9, but not in v5.10-rc1.
Bisection says it was broken by commit 90d46d71cce279d8 ("opp: Handle
multiple calls for same OPP table in _of_add_opp_table_v1()").
> > cpu cpu0: dev_pm_opp_get_opp_count:331
> > cpu cpu0: dev_pm_opp_get_opp_count:333: _find_opp_table() returned (ptrval)
> > cpu cpu0: dev_pm_opp_get_opp_count:342: _get_opp_count() returned 0
> > cpu cpu0: OPP table can't be empty
> >
> > Wait, _get_opp_count() returns 0?
>
> Does this fix it for you as well ?
>
> https://lore.kernel.org/lkml/2c73ab54717ef358b118ea0cfb727b1427e7730a.1602648719.git.viresh.kumar@linaro.org/
Thanks, it does. I had arrived at the same conclusion after bisection.
> I didn't point you to this earlier as your logs said something else.
All my logs said _get_opp_count() returns 0.
> > During s2ram, v5.10-rc1, it redoes most of the above, incl. touching the
> > PMIC, which it shouldn't due in this phase of system resume:
> >
> > Disabling non-boot CPUs ...
> > Enabling non-boot CPUs ...
> > cpufreq_dt: cpufreq_init:112: policy->cpu = 1
> > cpufreq_dt: cpufreq_init:113: policy->cpus = 1
> > cpufreq_dt: cpufreq_init:114: policy->related_cpus =
> > cpufreq_dt: cpufreq_init:115: policy->real_cpus =
> > of: dev_pm_opp_of_cpumask_add_table:1075
> > of: dev_pm_opp_of_cpumask_add_table:1080: cpu 0
> > cpu cpu0: dev_pm_opp_of_add_table:980
> > cpu cpu0: dev_pm_opp_of_add_table:982:
> > dev_pm_opp_get_opp_table_indexed() returned f680980b
> > cpu cpu0: _of_add_opp_table_v1:914
> > cpu cpu0: _of_add_opp_table_v1:916: _find_opp_table() returned a4afd426
> > cpu cpu0: _of_add_opp_table_v1:937: 6 entries
> > i2c-sh_mobile e60b0000.i2c: Transfer request timed out
> >
> > The i2c controller is suspended, this could go boom...
> >
> > i2c-sh_mobile e60b0000.i2c: Transfer request timed out
> > i2c-sh_mobile e60b0000.i2c: Transfer request timed out
> > i2c-sh_mobile e60b0000.i2c: Transfer request timed out
> > i2c-sh_mobile e60b0000.i2c: Transfer request timed out
> > i2c-sh_mobile e60b0000.i2c: Transfer request timed out
> > of: dev_pm_opp_of_cpumask_add_table:1080: cpu 1
> > cpu cpu1: dev_pm_opp_of_add_table:980
> > cpu cpu1: dev_pm_opp_of_add_table:982:
> > dev_pm_opp_get_opp_table_indexed() returned f680980b
> > cpu cpu1: _of_add_opp_table_v1:914
> > cpu cpu1: _of_add_opp_table_v1:916: _find_opp_table() returned 9087c76d
> > cpu cpu1: _of_add_opp_table_v1:937: 6 entries
> > i2c-sh_mobile e60b0000.i2c: Transfer request timed out
> > i2c-sh_mobile e60b0000.i2c: Transfer request timed out
> > i2c-sh_mobile e60b0000.i2c: Transfer request timed out
> > i2c-sh_mobile e60b0000.i2c: Transfer request timed out
> > i2c-sh_mobile e60b0000.i2c: Transfer request timed out
> > i2c-sh_mobile e60b0000.i2c: Transfer request timed out
> > cpu cpu0: dev_pm_opp_get_opp_count:331
> > cpu cpu0: dev_pm_opp_get_opp_count:333: _find_opp_table() returned f680980b
> > cpu cpu0: dev_pm_opp_get_opp_count:342: _get_opp_count() returned 0
> > cpu cpu0: OPP table can't be empty
> > CPU1 is up
>
> Lets make the normal boot work first and see about this later.
This is also fixed by your patch: the PMIC is no longer accessed while
suspended.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2020-10-28 23:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 9:09 [PATCH V2 1/2] opp: Allow dev_pm_opp_get_opp_table() to return -EPROBE_DEFER Viresh Kumar
2020-08-24 9:09 ` [PATCH V2 2/2] cpufreq: dt: Refactor initialization to handle probe deferral properly Viresh Kumar
[not found] ` <CGME20200901085708eucas1p231ccacd7b41685ece92ee21e3b726f28@eucas1p2.samsung.com>
2020-09-01 8:57 ` Marek Szyprowski
2020-09-01 9:45 ` Viresh Kumar
2020-09-01 10:05 ` Marek Szyprowski
2020-09-01 10:12 ` Viresh Kumar
2020-10-13 9:47 ` Geert Uytterhoeven
2020-10-13 9:56 ` Viresh Kumar
2020-10-14 16:40 ` Geert Uytterhoeven
2020-10-16 5:03 ` Viresh Kumar
2020-10-16 6:44 ` Geert Uytterhoeven
2020-10-16 8:07 ` Viresh Kumar
2020-10-27 16:29 ` Geert Uytterhoeven
2020-10-28 5:48 ` Viresh Kumar
2020-10-28 9:49 ` Geert Uytterhoeven [this message]
2020-10-28 9:52 ` Viresh Kumar
2020-08-24 9:17 ` [PATCH V2 1/2] opp: Allow dev_pm_opp_get_opp_table() to return -EPROBE_DEFER Krzysztof Kozlowski
2020-08-24 11:08 ` Ulf Hansson
2020-08-24 11:39 ` Stephan Gerhold
2020-10-15 18:05 ` Sudeep Holla
2020-10-16 4:24 ` Viresh Kumar
2020-10-16 6:00 ` Sudeep Holla
2020-10-16 11:12 ` Sudeep Holla
2020-10-16 15:28 ` Stephan Gerhold
2020-10-19 4:58 ` Viresh Kumar
2020-10-19 9:17 ` Sudeep Holla
2020-10-19 9:24 ` Viresh Kumar
2020-10-19 10:12 ` Sudeep Holla
2020-10-19 10:35 ` Viresh Kumar
2020-10-19 14:10 ` Sudeep Holla
2020-10-20 5:05 ` Viresh Kumar
2020-10-20 5:54 ` Viresh Kumar
2020-10-20 9:37 ` Sudeep Holla
2020-10-20 9:41 ` Viresh Kumar
2020-10-20 9:52 ` Sudeep Holla
2020-10-20 9:59 ` Viresh Kumar
2020-10-27 22:24 ` Guenter Roeck
2020-10-28 4:06 ` Viresh Kumar
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=CAMuHMdXnfG8riHYsd9PYSHTDvJ11zQ27y_JJh_9+obUxxLen0g@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=broonie@kernel.org \
--cc=georgi.djakov@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=nks@flawful.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@kernel.org \
--cc=stephan@gerhold.net \
--cc=ulf.hansson@linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=wsa@the-dreams.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).