On Sun, Nov 21, 2021 at 01:24:09PM +0100, Greg KH wrote: > On Sat, Nov 20, 2021 at 03:17:02PM -0800, David E. Box wrote: > > Add #defines for accessing Vendor ID, Revision, Length, and ID offsets > > in the Designated Vendor Specific Extended Capability (DVSEC). Defined > > in PCIe r5.0, sec 7.9.6. > > > > Signed-off-by: David E. Box <david.e.box@xxxxxxxxxxxxxxx> > > Acked-by: Bjorn Helgaas <bhelgaas@xxxxxxxxxx> > > Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx> > > --- > > include/uapi/linux/pci_regs.h | 4 ++++ > > 1 file changed, 4 insertions(+) > > > > diff --git a/include/uapi/linux/pci_regs.h b/include/uapi/linux/pci_regs.h > > index ff6ccbc6efe9..318f3f1f9e92 100644 > > --- a/include/uapi/linux/pci_regs.h > > +++ b/include/uapi/linux/pci_regs.h > > @@ -1086,7 +1086,11 @@ > > > > /* Designated Vendor-Specific (DVSEC, PCI_EXT_CAP_ID_DVSEC) */ > > #define PCI_DVSEC_HEADER1 0x4 /* Designated Vendor-Specific Header1 */ > > +#define PCI_DVSEC_HEADER1_VID(x) ((x) & 0xffff) > > +#define PCI_DVSEC_HEADER1_REV(x) (((x) >> 16) & 0xf) > > +#define PCI_DVSEC_HEADER1_LEN(x) (((x) >> 20) & 0xfff) > > #define PCI_DVSEC_HEADER2 0x8 /* Designated Vendor-Specific Header2 */ > > +#define PCI_DVSEC_HEADER2_ID(x) ((x) & 0xffff) > > Why does userspace need to have these defines? What userspace tool is > going to use these? This is pretty typical of other content in pci_regs.h. There's lots of existing content that may not be directly useful to userspace, but it's there because it's convenient to have definitions prescribed by the spec all together in one place. They probably shouldn't go in drivers/pci/pci.h because by definition this vendor-specific stuff will be used by vendor-specific drivers but not by the PCI core. I guess these *could* go in include/linux/pci.h, but that wouldn't be my first choice because there's nothing similar there. Bjorn
