drivers/gpu/drm/nouveau/nvkm/subdev/pci/gh100.c
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/nouveau/nvkm/subdev/pci/gh100.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/nouveau/nvkm/subdev/pci/gh100.c- Extension
.c- Size
- 654 bytes
- Lines
- 31
- Domain
- Driver Families
- Bucket
- drivers/gpu
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
priv.hnvhw/drf.hnvhw/ref/gh100/dev_xtl_ep_pri.h
Detected Declarations
function Copyrightfunction gh100_pci_new
Annotated Snippet
#include "priv.h"
#include <nvhw/drf.h>
#include <nvhw/ref/gh100/dev_xtl_ep_pri.h>
static void
gh100_pci_msi_rearm(struct nvkm_pci *pci)
{
/* Handled by top-level intr ACK. */
}
static const struct nvkm_pci_func
gh100_pci = {
.cfg = {
.addr = DRF_LO(NV_EP_PCFGM),
.size = DRF_HI(NV_EP_PCFGM) - DRF_LO(NV_EP_PCFGM) + 1,
},
.msi_rearm = gh100_pci_msi_rearm,
};
int
gh100_pci_new(struct nvkm_device *device, enum nvkm_subdev_type type, int inst,
struct nvkm_pci **ppci)
{
return nvkm_pci_new_(&gh100_pci, device, type, inst, ppci);
}
Annotation
- Immediate include surface: `priv.h`, `nvhw/drf.h`, `nvhw/ref/gh100/dev_xtl_ep_pri.h`.
- Detected declarations: `function Copyright`, `function gh100_pci_new`.
- Atlas domain: Driver Families / drivers/gpu.
- 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.