From: "Dragan Simic" <dsimic@manjaro.org>
To: "Geraldo Nascimento" <geraldogabriel@gmail.com>
Cc: "Shawn Lin" <shawn.lin@rock-chips.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>,
"Heiko Stuebner" <heiko@sntech.de>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Johan Jonker" <jbx6244@gmail.com>,
linux-rockchip@lists.infradead.org, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/4] PCI: rockchip: 5.0 GT/s speed may be dangerous
Date: Tue, 18 Nov 2025 07:45:45 +0100 [thread overview]
Message-ID: <e5d5c0dc-81d6-ae0e-7552-c2e4fb39bb0a@manjaro.org> (raw)
Hello Geraldo,
Thanks a lot for the v2! Please, see some comments below.
On Monday, November 17, 2025 22:46 CET, Geraldo Nascimento <geraldogabriel@gmail.com> wrote:
> Dragan Simic already had warned me of potential issues with 5.0 GT/s
> speed operation in Rockchip PCIe. However, in recent interactions
> with Shawn Lin from Rockchip it came to my attention there's grave
> danger in the unknown errata regarding 5.0 GT/s operational speed
> of their PCIe core. Even if the odds are low, to contain any damage,
> let's cover the remaining corner-cases where the default would lead
> to 5.0 GT/s operation as well as add a comment to Root Complex driver
> core, documenting this danger. Furthermore, remove redundant
> declaration of max-link-speed from rk3399-nanopi-r4s.dtsi
>
> Signed-off-by: Geraldo Nascimento <geraldogabriel@gmail.com>
As a note, Signed-off-by tags are redundant in cover letters, because
there's no source code in them that can actually be signed off.
> Changes in v2:
> - hard limit to 2.5 GT/s, not just warn
> - add Reported-by: and Reviewed-by: Dragan Simic
> - remove redundant declaration of max-link-speed from helios64 dts
> - fix Link: of helios64 patch
> - simplify RC mode comment
> - Link to v1: https://lore.kernel.org/all/aRhR79u5BPtRRFw3@geday/
Technically, you shouldn't have included my Reviewed-by tags in some
of the patches in the v2 of this series, because the patches were
either modified significantly since I gave my Reviewed-by for them
in the v1, or they were actually introduced in the v2.
However, I checked all four patches in the v2 again and everything
is still fine, so just to make sure, please feel free to include for
the entire series:
Reviewed-by: Dragan Simic <dsimic@manjaro.org>
> Geraldo Nascimento (4):
> PCI: rockchip: limit RK3399 to 2.5 GT/s to prevent damage
> PCI: rockchip-host: comment danger of 5.0 GT/s speed
> arm64: dts: rockchip: remove dangerous max-link-speed from helios64
> arm64: dts: rockchip: remove redundant max-link-speed from nanopi-r4s
>
> arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dts | 1 -
> arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dtsi | 1 -
> drivers/pci/controller/pcie-rockchip-host.c | 3 +++
> drivers/pci/controller/pcie-rockchip.c | 10 ++++++++--
> 4 files changed, 11 insertions(+), 4 deletions(-)
next reply other threads:[~2025-11-18 6:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 6:45 Dragan Simic [this message]
2025-11-18 7:17 ` Geraldo Nascimento
-- strict thread matches above, loose matches on Subject: below --
2025-11-17 21:46 Geraldo Nascimento
2025-11-18 0:43 ` Shawn Lin
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=e5d5c0dc-81d6-ae0e-7552-c2e4fb39bb0a@manjaro.org \
--to=dsimic@manjaro.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geraldogabriel@gmail.com \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=shawn.lin@rock-chips.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®