From: Rob Herring <robh@kernel.org>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
bhelgaas@google.com, Conor Dooley <conor+dt@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>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH 2/2] dt-bindings: updated max-link-speed for newer generations
Date: Wed, 7 Jun 2023 15:17:38 -0600 [thread overview]
Message-ID: <20230607211738.GA4076577-robh@kernel.org> (raw)
In-Reply-To: <20230531092121.291770-2-ben.dooks@codethink.co.uk>
On Wed, May 31, 2023 at 10:21:21AM +0100, Ben Dooks wrote:
> Add updated max-link-speed values for newer generation PCIe link
> speeds.
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
> Cc: devicetree@vger.kernel.org
> ---
> Documentation/devicetree/bindings/pci/pci.txt | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/pci/pci.txt b/Documentation/devicetree/bindings/pci/pci.txt
> index 6a8f2874a24d..56391e193fc4 100644
> --- a/Documentation/devicetree/bindings/pci/pci.txt
> +++ b/Documentation/devicetree/bindings/pci/pci.txt
> @@ -22,8 +22,9 @@ driver implementation may support the following properties:
> If present this property specifies PCI gen for link capability. Host
> drivers could add this as a strategy to avoid unnecessary operation for
> unsupported link speed, for instance, trying to do training for
> - unsupported link speed, etc. Must be '4' for gen4, '3' for gen3, '2'
> - for gen2, and '1' for gen1. Any other values are invalid.
> + unsupported link speed, etc. Must be '6' for gen6, '5' for gen5,
> + '4' for gen4, '3' for gen3, '2' for gen2, and '1' for gen1.
> + Any other values are invalid.
This file is a deadend to be removed.
Please update dtschema with the new values.
Rob
next prev parent reply other threads:[~2023-06-07 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 9:21 [PATCH 1/2] PCI: of: update max-link-speed for gen5 links Ben Dooks
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 [this message]
[not found] <ZHeZxPRGw+X83V1k@bhelgaas>
2023-06-06 12:21 ` Ben Dooks
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=20230607211738.GA4076577-robh@kernel.org \
--to=robh@kernel.org \
--cc=ben.dooks@codethink.co.uk \
--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=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-pci@vger.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).