include/media/ipu6-pci-table.h

File Facts

System

Linux kernel

Corpus path

include/media/ipu6-pci-table.h

Extension

.h

Size

876 bytes

Lines

29

Domain

Repository Root And Misc

Bucket

include

Inferred role

Repository Root And Misc: implementation source

Status

source implementation candidate

Why This File Exists

Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.

• Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/pci.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef __IPU6_PCI_TBL_H__
#define __IPU6_PCI_TBL_H__

#include <linux/pci.h>

#define PCI_DEVICE_ID_INTEL_IPU6		0x9a19
#define PCI_DEVICE_ID_INTEL_IPU6SE		0x4e19
#define PCI_DEVICE_ID_INTEL_IPU6EP_ADLP		0x465d
#define PCI_DEVICE_ID_INTEL_IPU6EP_ADLN		0x462e
#define PCI_DEVICE_ID_INTEL_IPU6EP_RPLP		0xa75d
#define PCI_DEVICE_ID_INTEL_IPU6EP_MTL		0x7d19

static const struct pci_device_id ipu6_pci_tbl[] = {
	{ PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IPU6) },
	{ PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IPU6SE) },
	{ PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IPU6EP_ADLP) },
	{ PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IPU6EP_ADLN) },
	{ PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IPU6EP_RPLP) },
	{ PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IPU6EP_MTL) },
	{ }
};

#endif /* __IPU6_PCI_TBL_H__ */

Annotation

• Immediate include surface: `linux/pci.h`.
• Atlas domain: Repository Root And Misc / include.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.