From: Bjorn Helgaas <helgaas@kernel.org>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com,
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>
Subject: Re: [PATCHv2] pci: add PCI_EXT_CAP_ID_PL_32GT define
Date: Wed, 31 May 2023 16:37:23 -0500 [thread overview]
Message-ID: <ZHe+E7+GOgnP2fmM@bhelgaas> (raw)
In-Reply-To: <20230531095713.293229-1-ben.dooks@codethink.co.uk>
On Wed, May 31, 2023 at 10:57:13AM +0100, Ben Dooks wrote:
> From: Ben Dooks <ben.dooks@sifive.com>
>
> Add the define for PCI_EXT_CAP_ID_PL_32GT for drivers that
> will want this whilst doing Gen5/Gen6 accesses.
>
> Signed-off-by: Ben Dooks <ben.dooks@sifive.com>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
I applied this to pci/enumeration for v6.5, thanks.
But I'm very curious about where you expect this to be used.
> --
> v2:
> - fixed tabs
> ---
> include/uapi/linux/pci_regs.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/uapi/linux/pci_regs.h b/include/uapi/linux/pci_regs.h
> index dc2000e0fe3a..e5f558d96493 100644
> --- a/include/uapi/linux/pci_regs.h
> +++ b/include/uapi/linux/pci_regs.h
> @@ -738,6 +738,7 @@
> #define PCI_EXT_CAP_ID_DVSEC 0x23 /* Designated Vendor-Specific */
> #define PCI_EXT_CAP_ID_DLF 0x25 /* Data Link Feature */
> #define PCI_EXT_CAP_ID_PL_16GT 0x26 /* Physical Layer 16.0 GT/s */
> +#define PCI_EXT_CAP_ID_PL_32GT 0x2A /* Physical Layer 32.0 GT/s */
> #define PCI_EXT_CAP_ID_DOE 0x2E /* Data Object Exchange */
> #define PCI_EXT_CAP_ID_MAX PCI_EXT_CAP_ID_DOE
>
> --
> 2.39.2
>
next prev parent reply other threads:[~2023-05-31 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 9:57 [PATCHv2] pci: add PCI_EXT_CAP_ID_PL_32GT define Ben Dooks
2023-05-31 21:37 ` Bjorn Helgaas [this message]
2023-06-02 13:08 ` Ben Dooks
2023-06-02 14:02 ` Bjorn Helgaas
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=ZHe+E7+GOgnP2fmM@bhelgaas \
--to=helgaas@kernel.org \
--cc=ben.dooks@codethink.co.uk \
--cc=ben.dooks@sifive.com \
--cc=bhelgaas@google.com \
--cc=greentime.hu@sifive.com \
--cc=jeegar.lakhani@sifive.com \
--cc=jude.onyenegecha@codethink.co.uk \
--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