linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	broonie@kernel.org
Subject: Re: About regression caused by commit aea6cb99703e ("regulator: resolve supply after creating regulator")
Date: Mon, 9 Nov 2020 07:28:13 +0800	[thread overview]
Message-ID: <858790f6-8b22-4fe7-bb74-56904ad203bd@suse.com> (raw)
In-Reply-To: <20201108171811.GB10914@qmqm.qmqm.pl>



On 2020/11/9 上午1:18, Michał Mirosław wrote:
> On Sun, Nov 08, 2020 at 03:35:33PM +0800, Qu Wenruo wrote:
>> Hi Michał,
>>
>> Recently when testing v5.10-rc2, I found my RK3399 boards failed to boot
>> from NVME.
>>
>> It turns out that, commit aea6cb99703e ("regulator: resolve supply after
>> creating regulator") seems to be the cause.
>>
>> In RK3399 board, vpcie1v8 and vpcie0v9 of the pcie controller is
>> provided by RK808 regulator.
>> With that commit, now RK808 regulator fails to register:
>>
>> [    1.402500] rk808-regulator rk808-regulator: there is no dvs0 gpio
>> [    1.403104] rk808-regulator rk808-regulator: there is no dvs1 gpio
>> [    1.419856] rk808 0-001b: failed to register 12 regulator
>> [    1.422801] rk808-regulator: probe of rk808-regulator failed with
>> error -22
> 
> Hi,
> 
> This looks lika the problem fixed by commit cf1ad559a20d ("regulator: defer
> probe when trying to get voltage from unresolved supply") recently accepted
> to regulator tree [1]. Can you verify this?

Thanks, tested with that commit cherry picked to v5.10-rc2 and it solves
the problem.

Thanks,
Qu
> 
> [1] git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next 
>  
> Best Regards
> Michał Mirosław
> 


  reply	other threads:[~2020-11-08 23:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-08  7:35 About regression caused by commit aea6cb99703e ("regulator: resolve supply after creating regulator") Qu Wenruo
2020-11-08  7:40 ` Qu Wenruo
2020-11-08 17:18 ` Michał Mirosław
2020-11-08 23:28   ` Qu Wenruo [this message]
2020-11-22 14:43     ` Jan Kiszka
2020-11-22 16:35       ` Michał Mirosław
2020-11-23  6:47         ` Jan Kiszka
2020-11-23  8:01           ` Qu Wenruo

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=858790f6-8b22-4fe7-bb74-56904ad203bd@suse.com \
    --to=wqu@suse.com \
    --cc=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mirq-linux@rere.qmqm.pl \
    /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).