drivers/video/fbdev/i810/i810-i2c.c

File Facts

System

Linux kernel

Corpus path

drivers/video/fbdev/i810/i810-i2c.c

Extension

.c

Size

5076 bytes

Lines

176

Domain

Driver Families

Bucket

drivers/video

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

• linux/module.h
• linux/kernel.h
• linux/delay.h
• linux/gfp.h
• linux/pci.h
• linux/fb.h
• i810.h
• i810_regs.h
• i810_main.h
• ../edid.h

Detected Declarations

• function Copyright
• function i810i2c_setsda
• function i810i2c_getscl
• function i810i2c_getsda
• function i810_setup_i2c_bus
• function i810_create_i2c_busses
• function i810_delete_i2c_busses
• function i810_probe_i2c_connector

Annotated Snippet

if (e != NULL) {
			DPRINTK("i810-i2c: Getting EDID from BIOS\n");
			edid = kmemdup(e, EDID_LENGTH, GFP_KERNEL);
		}
	}

	*out_edid = edid;

        return (edid) ? 0 : 1;
}

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/delay.h`, `linux/gfp.h`, `linux/pci.h`, `linux/fb.h`, `i810.h`, `i810_regs.h`.
• Detected declarations: `function Copyright`, `function i810i2c_setsda`, `function i810i2c_getscl`, `function i810i2c_getsda`, `function i810_setup_i2c_bus`, `function i810_create_i2c_busses`, `function i810_delete_i2c_busses`, `function i810_probe_i2c_connector`.
• Atlas domain: Driver Families / drivers/video.
• 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.