[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <cover.1762150971.git.geraldogabriel@gmail.com>
Date: Mon, 3 Nov 2025 03:26:35 -0300
From: Geraldo Nascimento <geraldogabriel@...il.com>
To: linux-rockchip@...ts.infradead.org
Cc: Shawn Lin <shawn.lin@...k-chips.com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Krzysztof WilczyĆski <kwilczynski@...nel.org>,
Manivannan Sadhasivam <mani@...nel.org>,
Rob Herring <robh@...nel.org>, Bjorn Helgaas <bhelgaas@...gle.com>,
Heiko Stuebner <heiko@...ech.de>, linux-pci@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Johan Jonker <jbx6244@...il.com>,
Geraldo Nascimento <geraldogabriel@...il.com>
Subject: [RFC PATCH 0/2] PCI: rockchip-host: support quirky devices
With these two changes I'm able to work with a Samsung PM981a OEM SSD
that is known to be not-working with Rockchip-IP PCIe.
Previously I attempted a contrived solution that mostly worked for my
simple purposes but was rather inelegant and impractical.
Now I have isolated the behavior to the three lines in the two commits.
Omit those three lines and you get a working set with the kernel.
I have no idea how to actually implement this in a way that makes sense
and doesn't break the PCIe spec but it is my sincere wish that
interested RK3399 parties test the change and report any regressions
with already-working devices and specifically, successes or failures of
initial link-training with these changes.
Geraldo Nascimento (2):
arm64: dts: rockchip: drop PCIe 3v3 always-on/boot-on
PCI: rockchip-host: drop wait on PERST# toggle
arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi | 2 --
drivers/pci/controller/pcie-rockchip-host.c | 1 -
2 files changed, 3 deletions(-)
--
2.49.0
Powered by blists - more mailing lists