From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Dragan Simic <dsimic@manjaro.org>
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>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Johan Jonker" <jbx6244@gmail.com>,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 0/3] PCI: rockchip: 5.0 GT/s speed may be dangerous
Date: Mon, 17 Nov 2025 04:02:28 -0300 [thread overview]
Message-ID: <aRrIhA1uv_aIneOc@geday> (raw)
In-Reply-To: <257951b7-c22e-9707-6aba-3dc5794306bb@manjaro.org>
On Mon, Nov 17, 2025 at 04:57:11AM +0100, Dragan Simic wrote:
> Hello Shawn and Geraldo,
>
> On Monday, November 17, 2025 04:42 CET, Shawn Lin <shawn.lin@rock-chips.com> wrote:
> > 在 2025/11/15 星期六 17:10, Geraldo Nascimento 写道:
> > > In recent interactions with Shawn Lin from Rockchip it came to my
> > > attention there's an unknown errata regarding 5.0 GT/s operational
> > > speed of their PCIe core. According to Shawn there's grave danger
> > > 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.
> >
> > I'm not sure just adding a warn would be a good choice. Could we totally
> > force to use gen1 and add a warn if trying to use Gen2.
>
> I think that forcing 2.5 GT/s with an appropriate warning message
> is a good idea. That would be like some quirk that gets applied
> automatically, to prevent data corruption, while warning people
> who attempt to "overclock" the PCIe interface.
Hi Shawn and Dragan,
Alright, I'll send v2 with this suggestion in mind. So that driving the
core at 5.0 GT/s will require patching and compiling own kernel.
>
> > Meanwhile amend the commit message to add a reference
> > of RK3399 official datesheet[1] which says PCIe on RK3399 should only
> > support 2.5GT/s?
> >
> > [1]https://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf
>
Shawn, URLs have the bad habit of changing or simply disappearing, so I
don't think it's a good idea to put URL in the commit message.
Also, the datasheet just mentions that RK3399 supports only 2.5 GT/s,
it does not mention possible damage from driving the core at 5.0 GT/s.
> Also, rewording the patch summary as follows below may be good,
> because that would provide more details:
>
> PCI: rockchip: Warn about Gen2 5.0 GT/s on RK3399 being unsafe
>
> Or, if we'll go with the automatic downgrading, like this:
>
> PCI: rockchip: Limit RK3399 to Gen1 2.5 GT/s to prevent breakage
>
Dragan, these are good ones, thanks. Though I think I'll omit Gen1/Gen2
wording since I know how much Bjorn dislikes those terms.
Thanks,
Geraldo Nascimento
WARNING: multiple messages have this Message-ID (diff)
From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Dragan Simic <dsimic@manjaro.org>
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>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Johan Jonker" <jbx6244@gmail.com>,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 0/3] PCI: rockchip: 5.0 GT/s speed may be dangerous
Date: Mon, 17 Nov 2025 04:02:28 -0300 [thread overview]
Message-ID: <aRrIhA1uv_aIneOc@geday> (raw)
In-Reply-To: <257951b7-c22e-9707-6aba-3dc5794306bb@manjaro.org>
On Mon, Nov 17, 2025 at 04:57:11AM +0100, Dragan Simic wrote:
> Hello Shawn and Geraldo,
>
> On Monday, November 17, 2025 04:42 CET, Shawn Lin <shawn.lin@rock-chips.com> wrote:
> > 在 2025/11/15 星期六 17:10, Geraldo Nascimento 写道:
> > > In recent interactions with Shawn Lin from Rockchip it came to my
> > > attention there's an unknown errata regarding 5.0 GT/s operational
> > > speed of their PCIe core. According to Shawn there's grave danger
> > > 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.
> >
> > I'm not sure just adding a warn would be a good choice. Could we totally
> > force to use gen1 and add a warn if trying to use Gen2.
>
> I think that forcing 2.5 GT/s with an appropriate warning message
> is a good idea. That would be like some quirk that gets applied
> automatically, to prevent data corruption, while warning people
> who attempt to "overclock" the PCIe interface.
Hi Shawn and Dragan,
Alright, I'll send v2 with this suggestion in mind. So that driving the
core at 5.0 GT/s will require patching and compiling own kernel.
>
> > Meanwhile amend the commit message to add a reference
> > of RK3399 official datesheet[1] which says PCIe on RK3399 should only
> > support 2.5GT/s?
> >
> > [1]https://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf
>
Shawn, URLs have the bad habit of changing or simply disappearing, so I
don't think it's a good idea to put URL in the commit message.
Also, the datasheet just mentions that RK3399 supports only 2.5 GT/s,
it does not mention possible damage from driving the core at 5.0 GT/s.
> Also, rewording the patch summary as follows below may be good,
> because that would provide more details:
>
> PCI: rockchip: Warn about Gen2 5.0 GT/s on RK3399 being unsafe
>
> Or, if we'll go with the automatic downgrading, like this:
>
> PCI: rockchip: Limit RK3399 to Gen1 2.5 GT/s to prevent breakage
>
Dragan, these are good ones, thanks. Though I think I'll omit Gen1/Gen2
wording since I know how much Bjorn dislikes those terms.
Thanks,
Geraldo Nascimento
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-11-17 7:02 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 9:10 [PATCH 0/3] PCI: rockchip: 5.0 GT/s speed may be dangerous Geraldo Nascimento
2025-11-15 9:10 ` Geraldo Nascimento
2025-11-15 9:10 ` [PATCH 1/3] PCI: rockchip: warn of danger of 5.0 GT/s speeds Geraldo Nascimento
2025-11-15 9:10 ` Geraldo Nascimento
2025-11-15 9:24 ` Dragan Simic
2025-11-15 9:24 ` Dragan Simic
2025-11-15 9:49 ` Geraldo Nascimento
2025-11-15 9:49 ` Geraldo Nascimento
2025-11-15 9:10 ` [PATCH 2/3] PCI: rockchip-host: comment danger of 5.0 GT/s speed Geraldo Nascimento
2025-11-15 9:10 ` Geraldo Nascimento
2025-11-15 9:30 ` Dragan Simic
2025-11-15 9:30 ` Dragan Simic
2025-11-15 9:51 ` Geraldo Nascimento
2025-11-15 9:51 ` Geraldo Nascimento
2025-11-15 10:01 ` Dragan Simic
2025-11-15 10:01 ` Dragan Simic
2025-11-15 10:04 ` Geraldo Nascimento
2025-11-15 10:04 ` Geraldo Nascimento
2025-11-15 10:09 ` Dragan Simic
2025-11-15 10:09 ` Dragan Simic
2025-11-15 10:11 ` Geraldo Nascimento
2025-11-15 10:11 ` Geraldo Nascimento
2025-11-15 9:10 ` [PATCH 3/3] arm64: dts: rockchip: drop max-link-speed = <2> in helios64 PCIe Geraldo Nascimento
2025-11-15 9:10 ` Geraldo Nascimento
2025-11-15 9:36 ` Dragan Simic
2025-11-15 9:36 ` Dragan Simic
2025-11-15 9:42 ` Dragan Simic
2025-11-15 9:42 ` Dragan Simic
2025-11-15 9:55 ` Geraldo Nascimento
2025-11-15 9:55 ` Geraldo Nascimento
2025-11-15 10:03 ` Dragan Simic
2025-11-15 10:03 ` Dragan Simic
2025-11-15 9:53 ` Geraldo Nascimento
2025-11-15 9:53 ` Geraldo Nascimento
2025-11-17 3:42 ` [PATCH 0/3] PCI: rockchip: 5.0 GT/s speed may be dangerous Shawn Lin
2025-11-17 3:42 ` Shawn Lin
2025-11-17 3:57 ` Dragan Simic
2025-11-17 3:57 ` Dragan Simic
2025-11-17 7:02 ` Geraldo Nascimento [this message]
2025-11-17 7:02 ` Geraldo Nascimento
2025-11-17 15:59 ` Dragan Simic
2025-11-17 15:59 ` Dragan Simic
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=aRrIhA1uv_aIneOc@geday \
--to=geraldogabriel@gmail.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.