From: "Heiko Stübner" <heiko@sntech.de>
To: Vicente Bergas <vicencb@gmail.com>
Cc: "open list:ARM/Rockchip SoC..." <linux-rockchip@lists.infradead.org>
Subject: Re: PCIe missing on RK3399
Date: Wed, 11 Dec 2024 16:35:06 +0100 [thread overview]
Message-ID: <2855083.6YUMPnJmAY@diego> (raw)
In-Reply-To: <CAAMcf8A8Y1js5Xt5FDOwq=dTw82UuZar0P6DVsJDgngRxPmtBw@mail.gmail.com>
Am Mittwoch, 11. Dezember 2024, 16:10:21 CET schrieb Vicente Bergas:
> On Wed, Dec 11, 2024 at 2:36 PM Heiko Stübner <heiko@sntech.de> wrote:
> >
> > Hi Vicente,
>
> Hi Heiko,
> thanks for taking a look at it!
>
> > Am Mittwoch, 11. Dezember 2024, 13:55:01 CET schrieb Vicente Bergas:
> > > i've tested the Linux kernel 6.13-rc1 and rc2 and in both cases PCIe
> > > is not detected on the RK3399 platform (rk3399-gru-kevin), whereas the
> > > kernel version 6.12.3 works fine.
> > >
> > > 6.13 configuration is based on the same one as 6.12 and there aren't
> > > any significant PCI-related differences.
> > >
> > > The messages from dmesg on 6.13 don't show any PCI-related errors.
> > >
> > > Does somebody know what is going on?
> >
> > so I just booted a rk3399-puma-haikou with a pci-nvme-adapter in the
> > pcie slot. And I get:
> >
> > [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
> > [ 0.000000] Linux version 6.13.0-rc2-00101-g260ae63734ff-dirty (hstuebner@phil) (aarch64-linux-gnu-gcc (Debian 14.2.0-6) 14.2.0, GNU ld (GNU Binutils for Debian) 2.43.1) #1134 SMP PREEMPT Tue Dec 10 21:06:34 CET 2024
> > ...
> > [ 3.428114] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
> > [ 3.435978] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
> > [ 3.445478] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
> > [ 3.455298] rockchip-pcie f8000000.pcie: using DT '/pcie@f8000000' for 'ep' GPIO lookup
> >
> > So there seems to be not some general failure.
> >
> > Does
> > # ls /sys/devices/platform/f8000000.pcie
> > list some "waiting_for_supplies" or something?
>
> yes, indeed there is such a file in there:
>
> ### 6.13-rc2
> $ ls /sys/devices/platform/f8000000.pcie
> power
> driver_override
> modalias
> of_node
> subsystem
> supplier:platform:ff720000.gpio
> supplier:platform:ff770000.syscon:pcie-phy
> supplier:platform:ff780000.gpio
> supplier:platform:pinctrl
> supplier:platform:regulator-pp3300-wifi-bt
> supplier:platform:regulator-wlan-pd-n
> uevent
> waiting_for_supplier
>
> $ cat /sys/devices/platform/f8000000.pcie/waiting_for_supplier
> 1
>
> ### 6.12.3
> $ ls /sys/devices/platform/f8000000.pcie
> pci0000:00
> power
> driver
> driver_override
> modalias
> of_node
> subsystem
> supplier:phy:phy-ff770000.syscon:pcie-phy.5
> supplier:phy:phy-ff770000.syscon:pcie-phy.6
> supplier:phy:phy-ff770000.syscon:pcie-phy.7
> supplier:phy:phy-ff770000.syscon:pcie-phy.8
> supplier:platform:ff770000.syscon:pcie-phy
> supplier:platform:ff780000.gpio
> supplier:platform:pinctrl
> supplier:platform:pp3300-wifi-bt
> supplier:platform:pp900-ap
> supplier:platform:wlan-pd-n
> supplier:regulator:regulator.17
> supplier:regulator:regulator.23
> supplier:regulator:regulator.25
> uevent
>
> What does that mean?
waiting_for_supplier means that some supplier has not yet probed
and thus the driver also cannot probe yet.
But your 6.13-rc2 supplier list does look way too short. In my boot on
rk3399-puma-haikou above, I got:
$ ls /sys/devices/platform/f8000000.pcie
driver
driver_override
modalias
of_node
pci0000:00
power
subsystem
supplier:phy:phy-ff770000.syscon:pcie-phy.2
supplier:phy:phy-ff770000.syscon:pcie-phy.3
supplier:phy:phy-ff770000.syscon:pcie-phy.4
supplier:phy:phy-ff770000.syscon:pcie-phy.5
supplier:platform:ff770000.syscon:pcie-phy
supplier:platform:ff790000.gpio
supplier:platform:pinctrl
supplier:platform:regulator-dc-12v
supplier:platform:regulator-vcc3v3-baseboard
supplier:platform:regulator-vcca-0v9
supplier:platform:regulator-vcca-1v8
supplier:regulator:regulator.10
supplier:regulator:regulator.11
supplier:regulator:regulator.29
supplier:regulator:regulator.3
uevent
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-12-11 15:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 12:55 PCIe missing on RK3399 Vicente Bergas
2024-12-11 13:36 ` Heiko Stübner
2024-12-11 15:10 ` Vicente Bergas
2024-12-11 15:35 ` Heiko Stübner [this message]
2024-12-11 17:31 ` Vicente Bergas
2024-12-12 12:12 ` Vicente Bergas
2024-12-12 13:06 ` Heiko Stübner
2024-12-12 16:50 ` Vicente Bergas
2024-12-28 0:51 ` Vicente Bergas
2024-12-28 9:35 ` Johan Jonker
2025-01-13 21:02 ` Vicente Bergas
2025-01-16 14:36 ` [PATCH] arm64: dts: rockchip: fix fixed-regulator renames on rk3399-gru devices Heiko Stuebner
2025-01-17 0:44 ` Vicente Bergas
2025-02-03 8:15 ` Heiko Stuebner
2025-02-07 0:17 ` PCIe missing on RK3399 Trevor Woerner
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=2855083.6YUMPnJmAY@diego \
--to=heiko@sntech.de \
--cc=linux-rockchip@lists.infradead.org \
--cc=vicencb@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.