From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Siddharth Vadapalli" <s-vadapalli@ti.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Nishanth Menon" <nm@ti.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4] PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)
Date: Fri, 28 Jun 2024 11:53:42 +0530 [thread overview]
Message-ID: <7158c241-51f5-4034-8713-d56d8fcaa0f5@ti.com> (raw)
In-Reply-To: <e8aee86f-4f4e-47f7-a472-58a7c154ab06@siemens.com>
On Fri, Jun 28, 2024 at 08:14:41AM +0200, Jan Kiszka wrote:
> From: Kishon Vijay Abraham I <kishon@ti.com>
>
> Errata #i2037 in AM65x/DRA80xM Processors Silicon Revision 1.0
> (SPRZ452D_July 2018_Revised December 2019 [1]) mentions when an
> inbound PCIe TLP spans more than two internal AXI 128-byte bursts,
> the bus may corrupt the packet payload and the corrupt data may
> cause associated applications or the processor to hang.
>
> The workaround for Errata #i2037 is to limit the maximum read
> request size and maximum payload size to 128 bytes. Add workaround
> for Errata #i2037 here. The errata and workaround is applicable
> only to AM65x SR 1.0 and later versions of the silicon will have
> this fixed.
>
> [1] -> http://www.ti.com/lit/er/sprz452d/sprz452d.pdf
nitpick: The above link redirects to:
https://www.ti.com/lit/er/sprz452i/sprz452i.pdf
So it is still valid, but it might be a good idea to use the updated
link and also update the commit message accordingly:
Errata #i2037 in AM65x/DRA80xM Processors Silicon Revision 1.0
(SPRZ452I_JULY_2018_REVISED_MAY_2023 [1]) ...
The updated link also uses "https" instead of "http" which is better.
>
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> Signed-off-by: Achal Verma <a-verma1@ti.com>
> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Thank you for updating the patch.
Reviewed-by: Siddharth Vadapalli <s-vadapalli@ti.com>
[...]
Regards,
Siddharth.
prev parent reply other threads:[~2024-06-28 6:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 6:14 Jan Kiszka
2024-06-28 6:23 ` Siddharth Vadapalli [this message]
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=7158c241-51f5-4034-8713-d56d8fcaa0f5@ti.com \
--to=s-vadapalli@ti.com \
--cc=bhelgaas@google.com \
--cc=jan.kiszka@siemens.com \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--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
all inboxes | Powered by JetHome®