From: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
To: Yue Wang <yue.wang@Amlogic.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Linnaea Lavia <linnaea-von-lavia@live.com>,
FUKAUMI Naoki <naoki@radxa.com>,
Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] PCI: meson: Remove meson_pcie_link_up() timeout, message, speed check
Date: Thu, 18 Dec 2025 11:36:01 +0530 [thread overview]
Message-ID: <176603796183.17581.9416209133990924154.b4-ty@kernel.org> (raw)
In-Reply-To: <20251103221930.1831376-1-helgaas@kernel.org>
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@kernel.org>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2025-12-18 6:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 22:19 Bjorn Helgaas
2025-11-10 11:04 ` Neil Armstrong
2025-12-18 6:06 ` Manivannan Sadhasivam [this message]
2026-01-05 16:49 ` Martin Blumenstingl
2026-01-05 17:15 ` Manivannan Sadhasivam
2026-01-05 17:25 ` Bjorn Helgaas
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=176603796183.17581.9416209133990924154.b4-ty@kernel.org \
--to=manivannan.sadhasivam@oss.qualcomm.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=linnaea-von-lavia@live.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=naoki@radxa.com \
--cc=neil.armstrong@linaro.org \
--cc=stable@vger.kernel.org \
--cc=yue.wang@Amlogic.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
Powered by JetHome