From: Tony Lindgren <tony@atomide.com>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Maciej Purski <m.purski@samsung.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Carlos Hernandez <ceh@ti.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH] regulator: core: Pass max_uV value to regulator_set_voltage_rdev
Date: Fri, 28 Sep 2018 13:22:51 -0700 [thread overview]
Message-ID: <20180928202251.GM5662@atomide.com> (raw)
In-Reply-To: <95655644-ef41-f5bd-7e8e-a257d48cd020@gmail.com>
* Dmitry Osipenko <digetx@gmail.com> [180928 20:13]:
> Tony, could you please give a try to the patch below?
>
> Do the following:
>
> 1) git cherry-pick 696861761a58d8c93605b5663824929fb6540f16
> 2) git cherry-pick 456e7cdf3b1a14e2606b8b687385ab2e3f23a49a
> 3) Apply this patch:
Seems to be getting closer, system boots up and starts
init, but then I start getting tons of this on beagle-x15:
[ 17.089059] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 17.096342] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 17.103275] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 17.118139] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 17.125078] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 17.132105] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 17.148187] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 17.155265] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 17.162355] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 17.171111] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 17.178156] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 17.185240] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 17.197636] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 17.204597] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 17.211621] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 17.227466] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 17.234428] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 17.241467] cpufreq: __target_index: Failed to change cpu frequency: -22
...
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] regulator: core: Pass max_uV value to regulator_set_voltage_rdev
Date: Fri, 28 Sep 2018 13:22:51 -0700 [thread overview]
Message-ID: <20180928202251.GM5662@atomide.com> (raw)
In-Reply-To: <95655644-ef41-f5bd-7e8e-a257d48cd020@gmail.com>
* Dmitry Osipenko <digetx@gmail.com> [180928 20:13]:
> Tony, could you please give a try to the patch below?
>
> Do the following:
>
> 1) git cherry-pick 696861761a58d8c93605b5663824929fb6540f16
> 2) git cherry-pick 456e7cdf3b1a14e2606b8b687385ab2e3f23a49a
> 3) Apply this patch:
Seems to be getting closer, system boots up and starts
init, but then I start getting tons of this on beagle-x15:
[ 17.089059] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 17.096342] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 17.103275] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 17.118139] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 17.125078] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 17.132105] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 17.148187] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 17.155265] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 17.162355] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 17.171111] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 17.178156] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 17.185240] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 17.197636] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 17.204597] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 17.211621] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 17.227466] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 17.234428] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 17.241467] cpufreq: __target_index: Failed to change cpu frequency: -22
...
Regards,
Tony
next prev parent reply other threads:[~2018-09-28 20:22 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 22:15 Regression in Linux next again Tony Lindgren
2018-05-29 22:15 ` Tony Lindgren
2018-05-30 9:13 ` Mark Brown
2018-05-30 9:13 ` Mark Brown
2018-05-30 14:03 ` Maciej Purski
2018-05-30 14:03 ` Maciej Purski
2018-05-30 14:33 ` Mark Brown
2018-05-30 14:33 ` Mark Brown
2018-05-30 14:45 ` Tony Lindgren
2018-05-30 14:45 ` Tony Lindgren
2018-06-04 13:59 ` Maciej Purski
2018-06-04 13:59 ` Maciej Purski
2018-06-04 13:59 ` [PATCH 1/7] regulator: core: Add debug messages Maciej Purski
2018-06-04 13:59 ` Maciej Purski
2018-06-04 13:59 ` [PATCH 2/7] regulator: core: Add regulator_set_voltage_rdev() Maciej Purski
2018-06-04 13:59 ` Maciej Purski
2018-06-04 13:59 ` [PATCH 3/7] regulator: core: Use re-entrant locks Maciej Purski
2018-06-04 13:59 ` Maciej Purski
2018-06-04 13:59 ` [PATCH 4/7] regulator: core: Implement voltage balancing algorithm Maciej Purski
2018-06-04 13:59 ` Maciej Purski
2018-06-04 13:59 ` Maciej Purski
2018-06-04 13:59 ` [PATCH 5/7] regulator: core: Lock dependent regulators Maciej Purski
2018-06-04 13:59 ` Maciej Purski
2018-06-04 13:59 ` Maciej Purski
2018-06-04 14:20 ` Lucas Stach
2018-06-04 14:20 ` Lucas Stach
2018-06-18 12:37 ` Maciej Purski
2018-06-18 12:37 ` Maciej Purski
2018-06-04 13:59 ` [PATCH 6/7] regulator: core: Lock dependent regulators on regulator_enable() Maciej Purski
2018-06-04 13:59 ` Maciej Purski
2018-06-04 13:59 ` [PATCH 7/7] regulator: core: Enable voltage balancing Maciej Purski
2018-06-04 13:59 ` Maciej Purski
2018-06-04 23:13 ` kbuild test robot
2018-06-04 23:13 ` kbuild test robot
2018-06-04 23:13 ` kbuild test robot
2018-06-04 23:54 ` kbuild test robot
2018-06-04 23:54 ` kbuild test robot
2018-06-04 23:54 ` kbuild test robot
2018-06-05 4:45 ` Regression in Linux next again Tony Lindgren
2018-06-05 4:45 ` Tony Lindgren
2018-06-13 10:33 ` [PATCH v2] regulator: core: Enable voltage balancing Maciej Purski
2018-06-13 10:33 ` Maciej Purski
2018-06-15 11:29 ` Tony Lindgren
2018-06-15 11:29 ` Tony Lindgren
2018-06-18 13:17 ` Maciej Purski
2018-06-18 13:17 ` Maciej Purski
2018-06-18 14:08 ` [PATCH] regulator: core: Pass max_uV value to regulator_set_voltage_rdev Maciej Purski
2018-06-18 14:08 ` Maciej Purski
2018-07-02 8:05 ` Tony Lindgren
2018-07-02 8:05 ` Tony Lindgren
2018-09-28 20:09 ` Dmitry Osipenko
2018-09-28 20:09 ` Dmitry Osipenko
2018-09-28 20:09 ` Dmitry Osipenko
2018-09-28 20:09 ` Dmitry Osipenko
2018-09-28 20:22 ` Tony Lindgren [this message]
2018-09-28 20:22 ` Tony Lindgren
2018-09-28 20:36 ` Dmitry Osipenko
2018-09-28 20:36 ` Dmitry Osipenko
2018-09-28 22:26 ` Dmitry Osipenko
2018-09-28 22:26 ` Dmitry Osipenko
2018-09-28 22:26 ` Dmitry Osipenko
2018-09-28 22:41 ` Tony Lindgren
2018-09-28 22:41 ` Tony Lindgren
2018-09-28 23:17 ` Dmitry Osipenko
2018-09-28 23:17 ` Dmitry Osipenko
2018-09-28 23:17 ` Dmitry Osipenko
2018-09-28 23:51 ` Dmitry Osipenko
2018-09-28 23:51 ` Dmitry Osipenko
2018-09-28 23:51 ` Dmitry Osipenko
2018-09-29 0:27 ` Tony Lindgren
2018-09-29 0:27 ` Tony Lindgren
2018-09-29 0:44 ` Dmitry Osipenko
2018-09-29 0:44 ` Dmitry Osipenko
2018-10-01 7:25 ` Maciej Purski
2018-10-01 7:25 ` Maciej Purski
2018-10-01 13:34 ` Dmitry Osipenko
2018-10-01 13:34 ` Dmitry Osipenko
2018-05-30 14:53 ` Regression in Linux next again Naresh Kamboju
2018-05-30 14:53 ` Naresh Kamboju
2018-05-31 5:44 ` Naresh Kamboju
2018-05-31 5:44 ` Naresh Kamboju
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=20180928202251.GM5662@atomide.com \
--to=tony@atomide.com \
--cc=broonie@kernel.org \
--cc=ceh@ti.com \
--cc=digetx@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=m.purski@samsung.com \
--cc=m.szyprowski@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.