drivers/gpu/drm/nouveau/nvkm/subdev/iccsense/priv.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/nouveau/nvkm/subdev/iccsense/priv.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/nouveau/nvkm/subdev/iccsense/priv.h- Extension
.h- Size
- 768 bytes
- Lines
- 28
- 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
subdev/iccsense.hsubdev/bios/extdev.h
Detected Declarations
struct nvkm_iccsense_sensorstruct nvkm_iccsense_rail
Annotated Snippet
struct nvkm_iccsense_sensor {
struct list_head head;
int id;
enum nvbios_extdev_type type;
struct i2c_adapter *i2c;
u8 addr;
u16 config;
};
struct nvkm_iccsense_rail {
struct list_head head;
int (*read)(struct nvkm_iccsense *, struct nvkm_iccsense_rail *);
struct nvkm_iccsense_sensor *sensor;
u8 idx;
u8 mohm;
};
void nvkm_iccsense_ctor(struct nvkm_device *, enum nvkm_subdev_type, int, struct nvkm_iccsense *);
int nvkm_iccsense_new_(struct nvkm_device *, enum nvkm_subdev_type, int, struct nvkm_iccsense **);
#endif
Annotation
- Immediate include surface: `subdev/iccsense.h`, `subdev/bios/extdev.h`.
- Detected declarations: `struct nvkm_iccsense_sensor`, `struct nvkm_iccsense_rail`.
- 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.