All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH v1] include: pci_ids: Add Cavium devices
Date: Fri, 17 Jul 2020 08:06:22 +0200	[thread overview]
Message-ID: <20200717060622.1861028-1-sr@denx.de> (raw)

From: Suneel Garapati <sgarapati@marvell.com>

Add VendorID and DeviceID for supported devices on OcteonTX/TX2
platforms.

Signed-off-by: Suneel Garapati <sgarapati@marvell.com>
Reviewed-by: Stefan Roese <sr@denx.de>
Cc: Simon Glass <sjg@chromium.org>
Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
---
RFC -> v1:
- Added device IDs

 include/pci_ids.h | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/include/pci_ids.h b/include/pci_ids.h
index bd59578ccb..7ecedc7f04 100644
--- a/include/pci_ids.h
+++ b/include/pci_ids.h
@@ -2360,6 +2360,24 @@
 #define PCI_DEVICE_ID_ALTIMA_AC9100	0x03ea
 #define PCI_DEVICE_ID_ALTIMA_AC1003	0x03eb
 
+#define PCI_VENDOR_ID_CAVIUM		0x177d
+#define PCI_DEVICE_ID_CAVIUM_GPIO	0xa00a
+#define PCI_DEVICE_ID_CAVIUM_MPI	0xa00b
+#define PCI_DEVICE_ID_CAVIUM_EMMC	0xa010
+#define PCI_DEVICE_ID_CAVIUM_TWSI	0xa012
+#define PCI_DEVICE_ID_CAVIUM_SATA	0xa01c
+#define PCI_DEVICE_ID_CAVIUM_NIC	0xa01e
+#define PCI_DEVICE_ID_CAVIUM_BGX	0xa026
+#define PCI_DEVICE_ID_CAVIUM_SMI	0xa02b
+#define PCI_DEVICE_ID_CAVIUM_NICVF	0xa034
+#define PCI_DEVICE_ID_CAVIUM_BCH	0xa043
+#define PCI_DEVICE_ID_CAVIUM_BCHVF	0xa044
+#define PCI_DEVICE_ID_CAVIUM_NDF	0xa04f
+#define PCI_DEVICE_ID_CAVIUM_RGX	0xa054
+#define PCI_DEVICE_ID_CAVIUM_CGX	0xa059
+#define PCI_DEVICE_ID_CAVIUM_RVU_PF	0xa063
+#define PCI_DEVICE_ID_CAVIUM_RVU_AF	0xa065
+
 #define PCI_VENDOR_ID_BELKIN		0x1799
 #define PCI_DEVICE_ID_BELKIN_F5D7010V7	0x701f
 
-- 
2.27.0

             reply	other threads:[~2020-07-17  6:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17  6:06 Stefan Roese [this message]
2020-07-17 20:59 ` [PATCH v1] include: pci_ids: Add Cavium devices Tom Rini

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=20200717060622.1861028-1-sr@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.