drivers/media/usb/pvrusb2/pvrusb2-wm8775.c

File Facts

System

Linux kernel

Corpus path

drivers/media/usb/pvrusb2/pvrusb2-wm8775.c

Extension

.c

Size

893 bytes

Lines

44

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

• pvrusb2-wm8775.h
• pvrusb2-hdw-internal.h
• pvrusb2-debug.h
• linux/videodev2.h
• media/v4l2-common.h
• linux/errno.h

Detected Declarations

• function Copyright

Annotated Snippet

switch (hdw->input_val) {
		case PVR2_CVAL_INPUT_RADIO:
			input = 1;
			break;
		default:
			/* All other cases just use the second input */
			input = 2;
			break;
		}
		pvr2_trace(PVR2_TRACE_CHIPS, "subdev wm8775 set_input(val=%d route=0x%x)",
			   hdw->input_val, input);

		sd->ops->audio->s_routing(sd, input, 0, 0);
	}
}

Annotation

• Immediate include surface: `pvrusb2-wm8775.h`, `pvrusb2-hdw-internal.h`, `pvrusb2-debug.h`, `linux/videodev2.h`, `media/v4l2-common.h`, `linux/errno.h`.
• Detected declarations: `function Copyright`.
• 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.