From: Trevor Woerner <twoerner@gmail.com>
To: Vicente Bergas <vicencb@gmail.com>
Cc: "Heiko Stübner" <heiko@sntech.de>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>
Subject: Re: PCIe missing on RK3399
Date: Thu, 6 Feb 2025 19:17:49 -0500 [thread overview]
Message-ID: <20250207001749.GA33513@localhost> (raw)
In-Reply-To: <CAAMcf8DL27-PYdEJ4eX1-PJnQDWB0osgHR0gbHAcr_oRniWOOg@mail.gmail.com>
Hi,
On Wed 2024-12-11 @ 01:55:01 PM, Vicente Bergas wrote:
> Hi,
> 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?
I'm seeing something very similar on a different RK3399-based device. As such
the proposed patch won't work in my case.
I have the "Penta SATA HAT for Rock 4"[1] on a rock-pi-4a device running a
bunch of disks for me. When Yocto (master) switched from 6.6.y to 6.12.y this
HAT stopped working. Currently Yocto master carries recipes for both 6.6.y and
6.12.y so I'm able to pin the kernel to 6.6.y, but it would be nice to get
this fixed.
I only have one such setup, and it's running in "production", so I'm not
overly keen to take it offline for long periods for testing. But I'm willing
to do some investigation if there are suggestions to try.
Currently Yocto supports 6.6.74 and 6.12.11.
[1] https://shop.allnetchina.cn/products/penta-sata-hat-for-rock-pi-4
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2025-02-07 0:18 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
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 ` Trevor Woerner [this message]
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=20250207001749.GA33513@localhost \
--to=twoerner@gmail.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox