mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: matwey@sai.msu.ru
Subject: About the rockpi4 pcie controller failed to initialize problem in v5.10-rc2
Date: Sat, 7 Nov 2020 20:29:51 +0800	[thread overview]
Message-ID: <ca6213f8-8754-f77c-e1b3-10edccf2d81a@gmx.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 933 bytes --]

Hi guys,

I see your awesome contribution to support Rock Pi 4B.

However in recent rc (v5.10-rc2), I found that even with `vpcie1v8` and
`vpcie0v9` added, `regulartor_dev_lookup()` now just returns
-EPROBE_DEFER, preventing rockchip pcie controller to be initialized.

The full callchain is:

rockchip_pcie_parse_host_dt()
|- rockchip>vpcie1v8 = devm_regulator_get_optional(dev, "vpcie1v8");
   |- _regulator_get()
      |- regulator_dev_lookup()
         |- node = of_get_regulartor()
         |- if (!node) {
         |-     r = of_find_regulator(); /* No @r found */
         |-     return ERR_PTR(-EPROBE_DEFER);

This means we can't utilize PCIE controller completely.

But strangely, `vpcie12v` and `vpcie3v3` both initialized without problem.

Any clue on how the problem could happened? I guess it's some device
tree definition went crazy, but not familiar with device tree at all.

Thanks,
Qu


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2020-11-07 12:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ca6213f8-8754-f77c-e1b3-10edccf2d81a@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matwey@sai.msu.ru \
    /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

all inboxes | Powered by JetHome®