[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176603796183.17581.9416209133990924154.b4-ty@kernel.org>
Date: Thu, 18 Dec 2025 11:36:01 +0530
From: Manivannan Sadhasivam <manivannan.sadhasivam@....qualcomm.com>
To: Yue Wang <yue.wang@...ogic.com>,
Neil Armstrong <neil.armstrong@...aro.org>,
Kevin Hilman <khilman@...libre.com>,
Bjorn Helgaas <helgaas@...nel.org>
Cc: Jerome Brunet <jbrunet@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
Linnaea Lavia <linnaea-von-lavia@...e.com>,
FUKAUMI Naoki <naoki@...xa.com>,
Krishna Chaitanya Chundru <krishna.chundru@....qualcomm.com>,
linux-amlogic@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, Bjorn Helgaas <bhelgaas@...gle.com>,
stable@...r.kernel.org
Subject: Re: [PATCH] PCI: meson: Remove meson_pcie_link_up() timeout,
message, speed check
On Mon, 03 Nov 2025 16:19:26 -0600, Bjorn Helgaas wrote:
> Previously meson_pcie_link_up() only returned true if the link was in the
> L0 state. This was incorrect because hardware autonomously manages
> transitions between L0, L0s, and L1 while both components on the link stay
> in D0. Those states should all be treated as "link is active".
>
> Returning false when the device was in L0s or L1 broke config accesses
> because dw_pcie_other_conf_map_bus() fails if the link is down, which
> caused errors like this:
>
> [...]
Applied, thanks!
[1/1] PCI: meson: Remove meson_pcie_link_up() timeout, message, speed check
commit: 11647fc772e977c981259a63c4a2b7e2c312ea22
Best regards,
--
Manivannan Sadhasivam <mani@...nel.org>
Powered by blists - more mailing lists