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 15:41:09 -0700 [thread overview]
Message-ID: <20180928224109.GS5662@atomide.com> (raw)
In-Reply-To: <2c0132ff-ea0f-f19e-ebfb-a0d077565d2c@gmail.com>
* Dmitry Osipenko <digetx@gmail.com> [180928 22:31]:
> On 9/28/18 11:22 PM, Tony Lindgren wrote:
> > * 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:
>
> Tony, could you please try this one? Fixed couple more bugs, should be good now.
I'm still getting these errors after init:
[ 29.008665] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 29.015987] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 29.022967] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 29.031993] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 29.038932] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 29.045962] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 29.055588] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 29.062639] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 29.069569] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 29.086215] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 29.093366] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 29.100295] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 29.110370] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 29.118402] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
[ 29.125450] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 29.127884] palmas-usb 48070000.i2c:tps659038 at 58:tps659038_usb: GPIO lookup for consumer id
[ 29.136112] cpu cpu0: vbb failed for 1210000uV[min 950000uV max 1500000uV]
[ 29.140658] palmas-usb 48070000.i2c:tps659038 at 58:tps659038_usb: using device tree for GPIO lookup
[ 29.147728] cpu cpu0: vbb failed for 1060000uV[min 850000uV max 1500000uV]
...
Regards,
Tony
next prev parent reply other threads:[~2018-09-28 22:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 22:15 Regression in Linux next again Tony Lindgren
2018-05-30 9:13 ` Mark Brown
2018-05-30 14:03 ` Maciej Purski
2018-05-30 14:33 ` Mark Brown
2018-05-30 14:45 ` Tony Lindgren
[not found] ` <CGME20180604135952eucas1p292f7bcec405e6a1a6261031df36cad32@eucas1p2.samsung.com>
2018-06-04 13:59 ` Maciej Purski
[not found] ` <CGME20180604135952eucas1p2d76b6aa5d8fc9912113d519b48f7e99a@eucas1p2.samsung.com>
2018-06-04 13:59 ` [PATCH 1/7] regulator: core: Add debug messages Maciej Purski
[not found] ` <CGME20180604135952eucas1p2e3fdb68bf31e32b7c9557051671885a9@eucas1p2.samsung.com>
2018-06-04 13:59 ` [PATCH 2/7] regulator: core: Add regulator_set_voltage_rdev() Maciej Purski
[not found] ` <CGME20180604135953eucas1p2f2c9dd9581cd114d323c3d64afe5c308@eucas1p2.samsung.com>
2018-06-04 13:59 ` [PATCH 3/7] regulator: core: Use re-entrant locks Maciej Purski
[not found] ` <CGME20180604135953eucas1p2ec281df0793bc73e79f3000837abcb04@eucas1p2.samsung.com>
2018-06-04 13:59 ` [PATCH 4/7] regulator: core: Implement voltage balancing algorithm Maciej Purski
[not found] ` <CGME20180604135954eucas1p2156fed3300b5514a4efa2baf9e7b9bc5@eucas1p2.samsung.com>
2018-06-04 13:59 ` [PATCH 5/7] regulator: core: Lock dependent regulators Maciej Purski
2018-06-04 14:20 ` Lucas Stach
2018-06-18 12:37 ` Maciej Purski
[not found] ` <CGME20180604135954eucas1p2eeb77ada3ca97fecc6caec20d7e8397a@eucas1p2.samsung.com>
2018-06-04 13:59 ` [PATCH 6/7] regulator: core: Lock dependent regulators on regulator_enable() Maciej Purski
[not found] ` <CGME20180604135954eucas1p2bebd1c4970401bb957da228056f9a662@eucas1p2.samsung.com>
2018-06-04 13:59 ` [PATCH 7/7] regulator: core: Enable voltage balancing Maciej Purski
2018-06-04 23:13 ` kbuild test robot
2018-06-04 23:54 ` kbuild test robot
2018-06-05 4:45 ` Regression in Linux next again Tony Lindgren
[not found] ` <CGME20180613103622eucas1p1778ba2c2e5dd85ccb4c488bd0a38386d@eucas1p1.samsung.com>
2018-06-13 10:33 ` [PATCH v2] regulator: core: Enable voltage balancing Maciej Purski
2018-06-15 11:29 ` Tony Lindgren
2018-06-18 13:17 ` Maciej Purski
[not found] ` <CGME20180618140856eucas1p281619f9bf003655a3c2eac356216ab25@eucas1p2.samsung.com>
2018-06-18 14:08 ` [PATCH] regulator: core: Pass max_uV value to regulator_set_voltage_rdev Maciej Purski
2018-07-02 8:05 ` Tony Lindgren
2018-09-28 20:09 ` Dmitry Osipenko
2018-09-28 20:22 ` Tony Lindgren
2018-09-28 20:36 ` Dmitry Osipenko
2018-09-28 22:26 ` Dmitry Osipenko
2018-09-28 22:41 ` Tony Lindgren [this message]
2018-09-28 23:17 ` Dmitry Osipenko
2018-09-28 23:51 ` Dmitry Osipenko
2018-09-29 0:27 ` Tony Lindgren
2018-09-29 0:44 ` Dmitry Osipenko
2018-10-01 7:25 ` Maciej Purski
2018-10-01 13:34 ` Dmitry Osipenko
2018-05-30 14:53 ` Regression in Linux next again 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=20180928224109.GS5662@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).