drivers/media/common/b2c2/flexcop-eeprom.c

File Facts

System

Linux kernel

Corpus path

drivers/media/common/b2c2/flexcop-eeprom.c

Extension

.c

Size

3303 bytes

Lines

148

Domain

Driver Families

Bucket

drivers/media

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• flexcop.h

Detected Declarations

• function FlexcopII
• function eeprom_lrc_write
• function eeprom_writeKey
• function eeprom_readKey
• function eeprom_set_mac_addr
• function flexcop_eeprom_read
• function calc_lrc
• function flexcop_eeprom_request
• function flexcop_eeprom_lrc_read
• function flexcop_eeprom_check_mac_addr
• export flexcop_eeprom_check_mac_addr

Annotated Snippet

if (extended != 0) {
			err("TODO: extended (EUI64) MAC addresses aren't completely supported yet");
			ret = -EINVAL;
		} else
			memcpy(fc->dvb_adapter.proposed_mac,buf,6);
	}
	return ret;
}
EXPORT_SYMBOL(flexcop_eeprom_check_mac_addr);

Annotation

• Immediate include surface: `flexcop.h`.
• Detected declarations: `function FlexcopII`, `function eeprom_lrc_write`, `function eeprom_writeKey`, `function eeprom_readKey`, `function eeprom_set_mac_addr`, `function flexcop_eeprom_read`, `function calc_lrc`, `function flexcop_eeprom_request`, `function flexcop_eeprom_lrc_read`, `function flexcop_eeprom_check_mac_addr`.
• Atlas domain: Driver Families / drivers/media.
• Implementation status: integration 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.