mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* About the rockpi4 pcie controller failed to initialize problem in v5.10-rc2
@ 2020-11-07 12:29 Qu Wenruo
  0 siblings, 0 replies; only message in thread
From: Qu Wenruo @ 2020-11-07 12:29 UTC (permalink / raw)
  To: Linux ARM, Linux Kernel Mailing List; +Cc: matwey


[-- 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 --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2020-11-07 12:31 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-07 12:29 About the rockpi4 pcie controller failed to initialize problem in v5.10-rc2 Qu Wenruo

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®