From: Jon Hunter <jonathanh@nvidia.com>
To: Saravana Kannan <saravanak@google.com>
Cc: Marc Zyngier <maz@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Android Kernel Team <kernel-team@android.com>,
LKML <linux-kernel@vger.kernel.org>,
Jisheng Zhang <Jisheng.Zhang@synaptics.com>,
Kevin Hilman <khilman@baylibre.com>,
John Stultz <john.stultz@linaro.org>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
linux-tegra <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v1 0/5] Enable fw_devlink=on by default
Date: Thu, 14 Jan 2021 11:34:53 +0000 [thread overview]
Message-ID: <17703ac8-2238-0b64-3c98-ddadc7ae8a36@nvidia.com> (raw)
In-Reply-To: <CAGETcx8pdPnH1ndOCoi7Qyz8DDshCfMTzDLQM=oEaCjyds9reA@mail.gmail.com>
On 13/01/2021 21:29, Saravana Kannan wrote:
...
>> I am seeing the same problem on Tegra30 Cardhu A04 where several regulators
>> are continuously deferred and prevents the board from booting ...
>>
>> [ 2.518334] platform panel: probe deferral - supplier regulator@11 not ready
>>
>> [ 2.525503] platform regulator@1: probe deferral - supplier 4-002d not ready
>>
>> [ 2.533141] platform regulator@3: probe deferral - supplier regulator@101 not ready
>>
>> [ 2.540856] platform regulator@5: probe deferral - supplier regulator@101 not ready
>>
>> [ 2.548589] platform regulator@6: probe deferral - supplier regulator@101 not ready
>>
>> [ 2.556316] platform regulator@7: probe deferral - supplier regulator@101 not ready
>>
>> [ 2.564041] platform regulator@8: probe deferral - supplier regulator@101 not ready
>>
>> [ 2.571743] platform regulator@9: probe deferral - supplier regulator@101 not ready
>>
>> [ 2.579463] platform regulator@10: probe deferral - supplier regulator@101 not ready
>>
>> [ 2.587273] platform regulator@11: probe deferral - supplier regulator@101 not ready
>>
>> [ 2.595088] platform regulator@12: probe deferral - supplier regulator@104 not ready
>>
>> [ 2.603837] platform regulator@102: probe deferral - supplier regulator@104 not ready
>>
>> [ 2.611726] platform regulator@103: probe deferral - supplier regulator@104 not ready
>>
>> [ 2.620137] platform 3000.pcie: probe deferral - supplier regulator@5 not ready
>
> Looks like this is not the whole log? Do you see any "wait for
> supplier" logs? That's what all these boot issues should boil down to.
> And as usual, pointer to DT for this board please.
Ah yes I see ...
platform regulator@1: probe deferral - wait for supplier tps65911@2d
Yes the device-tree for this board can be found here [0]. Looks like
there is a circular dependency between the vddctrl_reg and vddcore_reg.
This is part of coupled regulators which have a two-way linkage [1]. So
this change appears to conflict with this.
Jon
[0]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/tegra30-cardhu-a04.dts
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/regulator/regulator.yaml#n129
--
nvpublic
next prev parent reply other threads:[~2021-01-14 11:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201218031703.3053753-1-saravanak@google.com>
2021-01-13 11:30 ` [PATCH v1 0/5] Enable fw_devlink=on by default Jon Hunter
2021-01-13 21:26 ` Saravana Kannan
2021-01-14 16:11 ` Jon Hunter
2021-01-14 16:47 ` Saravana Kannan
2021-01-14 16:56 ` Jon Hunter
2021-01-28 15:03 ` Jon Hunter
2021-01-28 17:27 ` Saravana Kannan
2021-02-11 0:02 ` Saravana Kannan
2021-02-11 15:03 ` Rafael J. Wysocki
2021-02-11 17:14 ` Saravana Kannan
2021-02-11 17:48 ` Rafael J. Wysocki
2021-02-12 3:04 ` Saravana Kannan
[not found] ` <X/dpkgTnUk+inKHK@kroah.com>
[not found] ` <e28e1f38d87c12a3c714a6573beba6e1@kernel.org>
2021-01-13 15:27 ` Jon Hunter
2021-01-13 21:29 ` Saravana Kannan
2021-01-14 11:34 ` Jon Hunter [this message]
2021-01-14 16:40 ` Saravana Kannan
2021-01-14 16:47 ` Jon Hunter
2021-01-14 16:52 ` Saravana Kannan
2021-01-14 18:55 ` Jon Hunter
2021-01-14 21:50 ` Saravana Kannan
2021-01-15 16:12 ` Jon Hunter
2021-01-15 17:44 ` Saravana Kannan
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=17703ac8-2238-0b64-3c98-ddadc7ae8a36@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=Jisheng.Zhang@synaptics.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maz@kernel.org \
--cc=nsaenzjulienne@suse.de \
--cc=rafael@kernel.org \
--cc=saravanak@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox