drivers/media/usb/dvb-usb-v2/mxl111sf-gpio.h

File Facts

System

Linux kernel

Corpus path

drivers/media/usb/dvb-usb-v2/mxl111sf-gpio.h

Extension

.h

Size

1025 bytes

Lines

38

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

• mxl111sf.h

Detected Declarations

• enum mxl111sf_mux_config

Annotated Snippet

#ifndef _DVB_USB_MXL111SF_GPIO_H_
#define _DVB_USB_MXL111SF_GPIO_H_

#include "mxl111sf.h"

int mxl111sf_set_gpio(struct mxl111sf_state *state, int gpio, int val);
int mxl111sf_init_port_expander(struct mxl111sf_state *state);

#define MXL111SF_GPIO_MOD_DVBT	0
#define MXL111SF_GPIO_MOD_MH	1
#define MXL111SF_GPIO_MOD_ATSC	2
int mxl111sf_gpio_mode_switch(struct mxl111sf_state *state, unsigned int mode);

enum mxl111sf_mux_config {
	PIN_MUX_DEFAULT = 0,
	PIN_MUX_TS_OUT_PARALLEL,
	PIN_MUX_TS_OUT_SERIAL,
	PIN_MUX_GPIO_MODE,
	PIN_MUX_TS_SERIAL_IN_MODE_0,
	PIN_MUX_TS_SERIAL_IN_MODE_1,
	PIN_MUX_TS_SPI_IN_MODE_0,
	PIN_MUX_TS_SPI_IN_MODE_1,
	PIN_MUX_TS_PARALLEL_IN,
	PIN_MUX_BT656_I2S_MODE,
};

int mxl111sf_config_pin_mux_modes(struct mxl111sf_state *state,
				  enum mxl111sf_mux_config pin_mux_config);

#endif /* _DVB_USB_MXL111SF_GPIO_H_ */

Annotation

• Immediate include surface: `mxl111sf.h`.
• Detected declarations: `enum mxl111sf_mux_config`.
• 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.