Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Sunil Goutham <sgoutham@marvell.com>,
	bhelgaas@google.com, linux-pci@vger.kernel.org,
	sunil.goutham@gmail.com
Subject: Re: [PATCH] PCI: Add Marvell Octeon devices to PCI IDs
Date: Tue, 15 Feb 2022 09:28:38 -0600	[thread overview]
Message-ID: <20220215152838.GA109355@bhelgaas> (raw)
In-Reply-To: <YguaAbHelW0/l9lm@unreal>

On Tue, Feb 15, 2022 at 02:18:09PM +0200, Leon Romanovsky wrote:
> On Mon, Feb 14, 2022 at 05:55:10PM +0530, Sunil Goutham wrote:
> > Add Marvell (Cavium) OcteonTx2 and CN10K devices
> > to PCI ID database.
> > 
> > Signed-off-by: Sunil Goutham <sgoutham@marvell.com>
> > ---
> >  include/linux/pci_ids.h | 15 +++++++++++++++
> >  1 file changed, 15 insertions(+)
> > 
> > diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> > index aad54c6..5fd187b 100644
> > --- a/include/linux/pci_ids.h
> > +++ b/include/linux/pci_ids.h
> > @@ -2357,6 +2357,21 @@
> >  #define PCI_DEVICE_ID_ALTIMA_AC1003	0x03eb
> >  
> >  #define PCI_VENDOR_ID_CAVIUM		0x177d
> > +#define PCI_DEVICE_ID_OCTEONTX2_PTP	0xA00C
> > +#define PCI_DEVICE_ID_CN10K_PTP		0xA09E
> > +#define PCI_DEVICE_ID_OCTEONTX2_CGX	0xA059
> > +#define PCI_DEVICE_ID_CN10K_RPM		0xA060
> > +#define PCI_DEVICE_ID_OCTEONTX2_CPTPF	0xA0FD
> > +#define PCI_DEVICE_ID_OCTEONTX2_CPTVF	0xA0FE
> > +#define PCI_DEVICE_ID_CN10K_CPTPF	0xA0F2
> > +#define PCI_DEVICE_ID_CN10K_CPTVF	0xA0F3
> > +#define PCI_DEVICE_ID_OCTEONTX2_RVUAF	0xA065
> > +#define PCI_DEVICE_ID_OCTEONTX2_RVUPF	0xA063
> > +#define PCI_DEVICE_ID_OCTEONTX2_RVUVF	0xA064
> > +#define PCI_DEVICE_ID_OCTEONTX2_LBK	0xA061
> > +#define PCI_DEVICE_ID_OCTEONTX2_LBKVF	0xA0F8
> > +#define PCI_DEVICE_ID_OCTEONTX2_SDPPF	0xA0F6
> > +#define PCI_DEVICE_ID_OCTEONTX2_SDPVF	0xA0F7
> 
> If I recall correctly, this file is for device IDs that are used in more
> than one subsystem. It is not supposed to be updated for every octeon device.

Right; if these are just used in one driver, the #define should go in
that driver to help make merges easier.  If they're used in several
places, they can go here.  But please:

  - Include patches to the users in the series
  - Include the "vendor" tag in the device #defines to avoid conflicts
  - Use lower-case hex to match the surrounding context

Also consider adding these to https://pci-ids.ucw.cz/ in any case,
which will make "lspci" show useful names.

Bjorn

      reply	other threads:[~2022-02-15 15:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 12:25 [PATCH] PCI: Add Marvell Octeon devices to PCI IDs Sunil Goutham
2022-02-15 12:18 ` Leon Romanovsky
2022-02-15 15:28   ` Bjorn Helgaas [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=20220215152838.GA109355@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=leon@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sgoutham@marvell.com \
    --cc=sunil.goutham@gmail.com \
    /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