drivers/media/pci/ddbridge/ddbridge-mci.c

File Facts

System

Linux kernel

Corpus path

drivers/media/pci/ddbridge/ddbridge-mci.c

Extension

.c

Size

4006 bytes

Lines

170

Domain

Driver Families

Bucket

drivers/media

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• ddbridge.h
• ddbridge-io.h
• ddbridge-mci.h

Detected Declarations

• function mci_reset
• function ddb_mci_config
• function _mci_cmd_unlocked
• function ddb_mci_cmd
• function mci_handler
• function probe
• function int

Annotated Snippet

if (probe(state) < 0) {
			kfree(base);
			goto fail;
		}
		list_add(&base->mci_list, &mci_list);
		if (cfg->base_init)
			cfg->base_init(base);
	}
	memcpy(&state->fe.ops, cfg->fe_ops, sizeof(struct dvb_frontend_ops));
	state->fe.demodulator_priv = state;
	state->nr = nr;
	*fn_set_input = cfg->set_input;
	state->tuner = nr;
	state->demod = nr;
	if (cfg->init)
		cfg->init(state);
	return &state->fe;
fail:
	kfree(state);
	return NULL;
}

Annotation

• Immediate include surface: `ddbridge.h`, `ddbridge-io.h`, `ddbridge-mci.h`.
• Detected declarations: `function mci_reset`, `function ddb_mci_config`, `function _mci_cmd_unlocked`, `function ddb_mci_cmd`, `function mci_handler`, `function probe`, `function int`.
• Atlas domain: Driver Families / drivers/media.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.