archive mirror
 help / color / mirror / Atom feed
From: Slark Xiao <>
	Slark Xiao <>
Subject: [PATCH v2] PCI: Add vendor ID for Quectel and Cinterion
Date: Fri, 28 Oct 2022 10:37:11 +0800	[thread overview]
Message-ID: <> (raw)

In MHI driver, there are some companies product still do not have their
 own PCI vendor macro. So we add it here to make the code neat. Ref ID
 could be found in link
 and . Thales use Cinterion as
their IOT modem card's trademark. So you will find 0x1269 belongs to
Thales. Actually, Cinterion belongs to Gemalto, and Gemalto belongs to

Signed-off-by: Slark Xiao <>
 include/linux/pci_ids.h | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index b362d90eb9b0..9e2b6286f53f 100644
--- a/include/linux/pci_ids.h
+++ b/include/linux/pci_ids.h
@@ -1765,6 +1765,8 @@
 #define PCI_VENDOR_ID_SATSAGEM		0x1267
+#define PCI_VENDOR_ID_CINTERION		0x1269	/* Celluar Modules*/
 #define PCI_VENDOR_ID_ENSONIQ		0x1274
 #define PCI_DEVICE_ID_ENSONIQ_CT5880	0x5880
 #define PCI_DEVICE_ID_ENSONIQ_ES1370	0x5000
@@ -2585,6 +2587,8 @@
 #define PCI_VENDOR_ID_TEKRAM		0x1de1
 #define PCI_DEVICE_ID_TEKRAM_DC290	0xdc29
+#define PCI_VENDOR_ID_QUECTEL		0x1eac
 #define PCI_VENDOR_ID_TEHUTI		0x1fc9
 #define PCI_DEVICE_ID_TEHUTI_3009	0x3009
 #define PCI_DEVICE_ID_TEHUTI_3010	0x3010

             reply	other threads:[~2022-10-28  2:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28  2:37 Slark Xiao [this message]
2022-10-28  3:51 ` [PATCH v2] PCI: Add vendor ID for Quectel and Cinterion Bagas Sanjaya
2022-10-28  3:57   ` Slark Xiao
2022-10-28  4:00     ` Bagas Sanjaya
2022-10-28 16:06 ` Bjorn Helgaas
2022-10-31  9:08   ` Slark Xiao
2022-10-31 14:58     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).