From: "Heiko Stübner" <heiko@sntech.de>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org,
Shawn Lin <shawn.lin@rock-chips.com>,
Andrew Powers-Holmes <aholmes@omnom.net>
Subject: Re: [PATCH 1/2] arm64: dts: rockchip: Fix rk356x PCIe range mappings
Date: Wed, 04 Feb 2026 20:11:38 +0100 [thread overview]
Message-ID: <4208259.Y6S9NjorxK@diego> (raw)
In-Reply-To: <1767600929-195341-1-git-send-email-shawn.lin@rock-chips.com>
Am Montag, 5. Januar 2026, 09:15:28 Mitteleuropäische Normalzeit schrieb Shawn Lin:
> The pcie bus address should be mapped 1:1 to the cpu side MMIO address, so
> that there is no same address allocated from normal system memory. Otherwise
> it's broken if the same address assigned to the EP for DMA purpose.Fix it to
> sync with the vendor BSP.
>
> Fixes: 568a67e742df ("arm64: dts: rockchip: Fix rk356x PCIe register and range mappings")
> Fixes: 66b51ea7d70f ("arm64: dts: rockchip: Add rk3568 PCIe2x1 controller")
> Cc: Andrew Powers-Holmes <aholmes@omnom.net>
> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
somehow I seem to have forgotten to send the "applied" mail.
Anyway, both patches were applied 2 weeks ago, and are on their way
to the next merge-window.
With their stable-tags, they then should also migrate to older kernels.
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2026-02-04 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 8:15 [PATCH 1/2] arm64: dts: rockchip: Fix rk356x PCIe range mappings Shawn Lin
2026-01-05 8:15 ` [PATCH 2/2] arm64: dts: rockchip: Fix rk3588 " Shawn Lin
2026-01-20 9:44 ` [PATCH 1/2] arm64: dts: rockchip: Fix rk356x " Heiko Stuebner
2026-01-20 10:14 ` Shawn Lin
2026-02-04 19:11 ` Heiko Stübner [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=4208259.Y6S9NjorxK@diego \
--to=heiko@sntech.de \
--cc=aholmes@omnom.net \
--cc=linux-rockchip@lists.infradead.org \
--cc=shawn.lin@rock-chips.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