drivers/media/dvb-frontends/tda8261_cfg.h

File Facts

System

Linux kernel

Corpus path

drivers/media/dvb-frontends/tda8261_cfg.h

Extension

.h

Size

1226 bytes

Lines

50

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• function tda8261_get_frequency
• function tda8261_set_frequency
• function tda8261_get_bandwidth

Annotated Snippet

if (err < 0) {
			pr_err("%s: Invalid parameter\n", __func__);
			return err;
		}
		pr_debug("%s: Frequency=%d\n", __func__, *frequency);
	}
	return 0;
}

static int tda8261_set_frequency(struct dvb_frontend *fe, u32 frequency)
{
	struct dvb_frontend_ops	*frontend_ops = &fe->ops;
	struct dvb_tuner_ops	*tuner_ops = &frontend_ops->tuner_ops;
	struct dtv_frontend_properties *c = &fe->dtv_property_cache;
	int err = 0;

	if (tuner_ops->set_params) {
		err = tuner_ops->set_params(fe);
		if (err < 0) {
			pr_err("%s: Invalid parameter\n", __func__);
			return err;
		}
	}
	pr_debug("%s: Frequency=%d\n", __func__, c->frequency);
	return 0;
}

static int tda8261_get_bandwidth(struct dvb_frontend *fe, u32 *bandwidth)
{
	/* FIXME! need to calculate Bandwidth */
	*bandwidth = 40000000;

	return 0;
}

Annotation

• Detected declarations: `function tda8261_get_frequency`, `function tda8261_set_frequency`, `function tda8261_get_bandwidth`.
• Atlas domain: Driver Families / drivers/media.
• 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.