From: Hans Zhang <18255117159@163.com>
To: bhelgaas@google.com, lpieralisi@kernel.org, kw@linux.com,
krzk+dt@kernel.org, manivannan.sadhasivam@linaro.org,
conor+dt@kernel.org
Cc: robh@kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 3/3] PCI: of: Relax max-link-speed check to support PCIe Gen5/Gen6
Date: Sun, 17 Aug 2025 00:05:17 +0800 [thread overview]
Message-ID: <953620e7-8873-481d-b235-8cbefcb08172@163.com> (raw)
In-Reply-To: <20250529021026.475861-4-18255117159@163.com>
Dear Bjorn,
Gentle ping.
Best regards,
Hans
On 2025/5/29 10:10, Hans Zhang wrote:
> The existing code restricted `max-link-speed` to values 1~4 (Gen1~Gen4),
> but current SOCs using Synopsys/Cadence IP may require Gen5/Gen6 support.
> This patch updates the validation in `of_pci_get_max_link_speed` to allow
> values up to 6, ensuring compatibility with newer PCIe generations.
>
> Signed-off-by: Hans Zhang <18255117159@163.com>
> ---
> drivers/pci/of.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pci/of.c b/drivers/pci/of.c
> index ab7a8252bf41..379d90913937 100644
> --- a/drivers/pci/of.c
> +++ b/drivers/pci/of.c
> @@ -890,7 +890,7 @@ int of_pci_get_max_link_speed(struct device_node *node)
> u32 max_link_speed;
>
> if (of_property_read_u32(node, "max-link-speed", &max_link_speed) ||
> - max_link_speed == 0 || max_link_speed > 4)
> + max_link_speed == 0 || max_link_speed > 6)
> return -EINVAL;
>
> return max_link_speed;
next prev parent reply other threads:[~2025-08-16 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 2:10 [PATCH v2 0/3] " Hans Zhang
2025-05-29 2:10 ` [PATCH v2 1/3] dt-bindings: PCI: Extend max-link-speed " Hans Zhang
2025-06-17 16:45 ` Manivannan Sadhasivam
2025-06-18 14:22 ` Hans Zhang
2025-06-28 15:40 ` Hans Zhang
2025-05-29 2:10 ` [PATCH v2 2/3] dt-bindings: PCI: pci-ep: Extend max-link-speed to " Hans Zhang
2025-05-29 2:10 ` [PATCH v2 3/3] PCI: of: Relax max-link-speed check to support " Hans Zhang
2025-06-17 16:50 ` Manivannan Sadhasivam
2025-06-18 14:24 ` Hans Zhang
2025-08-16 16:05 ` Hans Zhang [this message]
2025-06-17 16:49 ` [PATCH v2 0/3] " Manivannan Sadhasivam
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=953620e7-8873-481d-b235-8cbefcb08172@163.com \
--to=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
/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®