linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Martin Mares <mj@ucw.cz>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/1] lspci: Add PCIe 6.0 data rate (64 GT/s) also to LnkCap2
Date: Fri, 8 Dec 2023 12:10:47 +0200 (EET)	[thread overview]
Message-ID: <2f56e555-b99c-48b3-6d8c-3fdb5bee6a1@linux.intel.com> (raw)
In-Reply-To: <20231208100631.2169-1-ilpo.jarvinen@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

On Fri, 8 Dec 2023, Ilpo Järvinen wrote:

> While commit cecfc33d9c8a ("lspci: Add PCIe 6.0 data rate (64 GT/s)

Please disregard this one! I'll send v2 with the correct hash (I played 
with my .gitconfig to get it always 12 char hashes and while doing so,
I managed to copy the wrong hash here).

-- 
 i.


> support") added 64 GT/s support to some registers, LnkCap2 Supported
> Link Speeds Vector was not included.
> 
> Add PCIe 6.0 data rate bit check also into
> cap_express_link2_speed_cap().
> 
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> ---
>  ls-caps.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/ls-caps.c b/ls-caps.c
> index fce9502bd29a..2c99812c4ed2 100644
> --- a/ls-caps.c
> +++ b/ls-caps.c
> @@ -1191,8 +1191,10 @@ static const char *cap_express_link2_speed_cap(int vector)
>     * permitted to skip support for any data rates between 2.5GT/s and the
>     * highest supported rate.
>     */
> -  if (vector & 0x60)
> +  if (vector & 0x40)
>      return "RsvdP";
> +  if (vector & 0x20)
> +    return "2.5-64GT/s";
>    if (vector & 0x10)
>      return "2.5-32GT/s";
>    if (vector & 0x08)
> 

      reply	other threads:[~2023-12-08 10:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 10:06 [PATCH 1/1] lspci: Add PCIe 6.0 data rate (64 GT/s) also to LnkCap2 Ilpo Järvinen
2023-12-08 10:10 ` Ilpo Järvinen [this message]

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=2f56e555-b99c-48b3-6d8c-3fdb5bee6a1@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=mj@ucw.cz \
    /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).