From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: <412574090@163.com>
Cc: <helgaas@kernel.org>, <bhelgaas@google.com>,
<linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<xiongxin@kylinos.cn>
Subject: Re: [PATCH] PCI: Add PCI_EXT_CAP_ID_PL_64GT define
Date: Thu, 8 Aug 2024 17:20:30 +0100 [thread overview]
Message-ID: <20240808172030.00006950@Huawei.com> (raw)
In-Reply-To: <20240808021239.24428-1-412574090@163.com>
On Thu, 8 Aug 2024 10:12:39 +0800
412574090@163.com wrote:
> > On Tue, Aug 06, 2024 at 10:27:46AM +0800, 412574090@163.com wrote:
> > > From: weiyufeng <weiyufeng@kylinos.cn>
> > >
> > > PCIe r6.0, sec 7.7.7.1, defines a new 64.0 GT/s PCIe Extended Capability
> > > ID,Add the define for PCI_EXT_CAP_ID_PL_64GT for drivers that will want
> > > this whilst doing Gen6 accesses.
> > >
> > > Signed-off-by: weiyufeng <weiyufeng@kylinos.cn>
> > > ---
> > > 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 94c00996e633..cc875534dae1 100644
> > > --- a/include/uapi/linux/pci_regs.h
> > > +++ b/include/uapi/linux/pci_regs.h
> > > @@ -741,6 +741,7 @@
> > > #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_PL_64GT 0x31 /* Physical Layer 64.0 GT/s */
> >
> > It probably makes sense to add this (with the corrections noted by
> > Ilpo), but I *would* like to see where it's used.
> >
> > I asked a similar question at
> > https://lore.kernel.org/all/20230531095713.293229-1-ben.dooks@codethink.co.uk/
> > when we added PCI_EXT_CAP_ID_PL_32GT, but never got a specific
> > response. I don't really want to end up with drivers doing their own
> > thing if it's something that could be done in the PCI core and shared.
> >
> PCI_EXT_CAP_ID_PL_32GT and PCI_EXT_CAP_ID_PL_64GT have not used now,but
> PCI_EXT_CAP_ID_PL_16GT have usage example,in drivers/pci/controller/dwc/pcie-tegra194.c
> function config_gen3_gen4_eq_presets():
>
> offset = dw_pcie_find_ext_capability(pci,
> PCI_EXT_CAP_ID_PL_16GT) +
> PCI_PL_16GT_LE_CTRL;
>
> PCI_EXT_CAP_ID_PL_32GT and PCI_EXT_CAP_ID_PL_64GT could be used while need to
> get this similar attribute。
I'll bite. In PCI_EXTE_CAP_ID_PL_32GT PCIe 6.1 which I happen to have
open has some writeable fields in the control register. So
kind of fair enough a driver might write them. In my view we should
probably have waited for such a use to turn up.
The Physical Layer 64.0 GT/s Extended Capability control register is
entirely reserved. So as of now, I don't see a use for this capability
until the PCIe spec adds something.
>
> > > #define PCI_EXT_CAP_ID_DOE 0x2E /* Data Object Exchange */
> > > #define PCI_EXT_CAP_ID_MAX PCI_EXT_CAP_ID_DOE
> > >
> > > --
> > > 2.25.1
> > >
> --
> Thanks,
>
> weiyufeng
>
>
prev parent reply other threads:[~2024-08-08 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 2:27 [PATCH] PCI: Add PCI_EXT_CAP_ID_PL_64GT define 412574090
2024-08-06 14:38 ` Ilpo Järvinen
2024-08-08 2:32 ` 412574090
2024-08-08 17:22 ` Bjorn Helgaas
2024-08-06 17:59 ` Bjorn Helgaas
2024-08-08 2:12 ` 412574090
2024-08-08 16:20 ` Jonathan Cameron [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=20240808172030.00006950@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=412574090@163.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=xiongxin@kylinos.cn \
/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