From: Bjorn Helgaas <helgaas@kernel.org>
To: Encrow Thorne <encrow.thorne@linux.spacemit.com>
Cc: "Troy Mitchell" <troy.mitchell@linux.spacemit.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Yixun Lan" <dlan@kernel.org>,
linux-pci@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: spacemit: Ignore link partner PERST on K1
Date: Thu, 5 Nov 2026 13:16:46 -0600 [thread overview]
Message-ID: <20261105191646.GA1549319@bhelgaas> (raw)
In-Reply-To: <DMMXR8IGD585.1QXMWPOMI19UL@linux.spacemit.com>
On Thu, Nov 05, 2026 at 10:53:05AM +0800, Encrow Thorne wrote:
> On Thu Sep 24, 2026 at 10:23 AM CST, Troy Mitchell wrote:
> > On Thu Sep 24, 2026 at 10:04 AM +08, Encrow Thorne wrote:
> >> The K1 PCIe controller and PHY are affected by the PERST signal from
> >> the link partner during initialization. With some devices connected,
> >> this can prevent host initialization from progressing and cause the
> >> system to hang while probing the PCIe controller.
> >>
> >> Set PCIE_IGNORE_PERSTN before accessing the DBI registers. When set,
> >> this bit makes both the PCIe controller and PHY ignore the PERST
> >> signal from the link partner.
> >>
> >> This allows host initialization to complete without being affected by
> >> the link partner's PERST state.
> >>
> >> Signed-off-by: Encrow Thorne <encrow.thorne@linux.spacemit.com>
> > Fix tag and reported-by tag [1]?
> >
> > Link: https://lore.kernel.org/all/20260825052249.66921-1-bbanelli@gmail.com/ [1]
>
> Thanks, I will add it in the next version.
If you haven't posted another version yet, s/PERST/PERST#/ in subject,
commit log, and comment to match spec usage.
next prev parent reply other threads:[~2026-11-05 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 2:04 Encrow Thorne
2026-09-24 2:23 ` Troy Mitchell
2026-11-05 2:53 ` Encrow Thorne
2026-11-05 19:16 ` Bjorn Helgaas [this message]
2026-10-18 4:26 ` Manivannan Sadhasivam
2026-11-05 2:51 ` Encrow Thorne
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=20261105191646.GA1549319@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=dlan@kernel.org \
--cc=encrow.thorne@linux.spacemit.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.spacemit.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
all inboxes | Powered by JetHome®