From: Ben Dooks <ben.dooks@codethink.co.uk>
To: devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
bhelgaas@google.com
Cc: Conor Dooley <conor+dt@kernel.org>, Rob Herring <robh@kernel.org>,
Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>,
Jude Onyenegecha <jude.onyenegecha@codethink.co.uk>,
Greentime Hu <greentime.hu@sifive.com>,
Jeegar Lakhani <jeegar.lakhani@sifive.com>,
Ben Dooks <ben.dooks@sifive.com>,
Ben Dooks <ben.dooks@codethink.co.uk>
Subject: [PATCH 1/2] PCI: of: update max-link-speed for gen5 links
Date: Wed, 31 May 2023 10:21:20 +0100 [thread overview]
Message-ID: <20230531092121.291770-1-ben.dooks@codethink.co.uk> (raw)
From: Ben Dooks <ben.dooks@sifive.com>
Update max-link-speed to be up to 6, for newer systems that could have
up to gen6 pci describe in device-tree.
Signed-off-by: Ben Dooks <ben.dooks@sifive.com>
Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
---
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 2c25f4fa0225..da0cc01e923e 100644
--- a/drivers/pci/of.c
+++ b/drivers/pci/of.c
@@ -639,7 +639,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;
--
2.39.2
next reply other threads:[~2023-05-31 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 9:21 Ben Dooks [this message]
2023-05-31 9:21 ` [PATCH 2/2] dt-bindings: updated max-link-speed for newer generations Ben Dooks
2023-06-06 19:36 ` Conor Dooley
2023-06-07 21:17 ` Rob Herring
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=20230531092121.291770-1-ben.dooks@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=ben.dooks@sifive.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=greentime.hu@sifive.com \
--cc=jeegar.lakhani@sifive.com \
--cc=jude.onyenegecha@codethink.co.uk \
--cc=linux-pci@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sudip.mukherjee@codethink.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).