[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dbaa721a-9a47-2c6a-46d5-92a7ca13c5aa@gmail.com>
Date: Sat, 29 Sep 2018 03:44:07 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Tony Lindgren <tony@...mide.com>
Cc: Maciej Purski <m.purski@...sung.com>,
Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-omap@...r.kernel.org,
Carlos Hernandez <ceh@...com>,
Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: [PATCH] regulator: core: Pass max_uV value to
regulator_set_voltage_rdev
On 9/29/18 3:27 AM, Tony Lindgren wrote:
> * Dmitry Osipenko <digetx@...il.com> [180928 23:55]:
>> On 9/29/18 2:17 AM, Dmitry Osipenko wrote:
>>> On 9/29/18 1:41 AM, Tony Lindgren wrote:
>>>> I'm still getting these errors after init:
>>>
>>> Thank you very much again, seems I got what's wrong with your case. The ti-abb-regulator driver sets the "abb->current_info_idx = -EINVAL" on probe and that value is getting updated only after the first voltage change, hence _regulator_get_voltage() returns -22.
>
> OK that's starting to make some sense now thanks.
>
>>> Please try this patch:
>>
>> I've revised the patch and here is the current final version.
>
> Hey cool this one works now :) I suggest you rework the whole series
> with these fixes. I recall the series had a problem with git bisect
> too between the patches. It will make life easier for other people
> who may need to git bisect these patches.
Awesome! There are few other things in this patchset that also need fixing. I've asked Maciej if he's going to continue working on the patches, waiting for the answer. I can pick up the patches and try to finish the work if necessary.
Powered by blists - more mailing lists