From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: tjoseph@cadence.com, robh@kernel.org, kw@linux.com,
bhelgaas@google.com, nadeem@cadence.com,
Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, vigneshr@ti.com,
srk@ti.com, nm@ti.com
Subject: Re: [PATCH v2] PCI: cadence: Fix Gen2 Link Retraining process
Date: Fri, 21 Apr 2023 11:09:22 +0200 [thread overview]
Message-ID: <168206814625.77926.12605918077768300523.b4-ty@kernel.org> (raw)
In-Reply-To: <20230315070800.1615527-1-s-vadapalli@ti.com>
On Wed, 15 Mar 2023 12:38:00 +0530, Siddharth Vadapalli wrote:
> The Link Retraining process is initiated to account for the Gen2 defect in
> the Cadence PCIe controller in J721E SoC. The errata corresponding to this
> is i2085, documented at:
> https://www.ti.com/lit/er/sprz455c/sprz455c.pdf
>
> The existing workaround implemented for the errata waits for the Data Link
> initialization to complete and assumes that the link retraining process
> at the Physical Layer has completed. However, it is possible that the
> Physical Layer training might be ongoing as indicated by the
> PCI_EXP_LNKSTA_LT bit in the PCI_EXP_LNKSTA register.
>
> [...]
Applied to controller/cadence, thanks!
[1/1] PCI: cadence: Fix Gen2 Link Retraining process
https://git.kernel.org/pci/pci/c/eac223e85208
Thanks,
Lorenzo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-04-21 9:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 7:08 [PATCH v2] PCI: cadence: Fix Gen2 Link Retraining process Siddharth Vadapalli
2023-03-29 14:41 ` Raghavendra, Vignesh
2023-03-29 17:08 ` Bjorn Helgaas
2023-03-30 4:22 ` Siddharth Vadapalli
2023-03-30 17:02 ` Bjorn Helgaas
2023-04-18 3:49 ` Siddharth Vadapalli
2023-04-21 8:57 ` Lorenzo Pieralisi
2023-03-30 8:45 ` Vignesh Raghavendra
2023-04-21 9:09 ` Lorenzo Pieralisi [this message]
[not found] <0ef69859-7ff9-1988-3c7e-692d8692b59f@ti.com>
2023-06-06 16:20 ` Bjorn Helgaas
2023-06-07 9:17 ` Siddharth Vadapalli
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=168206814625.77926.12605918077768300523.b4-ty@kernel.org \
--to=lpieralisi@kernel.org \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nadeem@cadence.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.com \
--cc=tjoseph@cadence.com \
--cc=vigneshr@ti.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