drivers/media/dvb-frontends/bcm3510.h
Source file repositories/reference/linux-study-clean/drivers/media/dvb-frontends/bcm3510.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/dvb-frontends/bcm3510.h- Extension
.h- Size
- 963 bytes
- Lines
- 37
- 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
linux/dvb/frontend.hlinux/firmware.h
Detected Declarations
struct bcm3510_configfunction bcm3510_attach
Annotated Snippet
#ifndef BCM3510_H
#define BCM3510_H
#include <linux/dvb/frontend.h>
#include <linux/firmware.h>
struct bcm3510_config
{
/* the demodulator's i2c address */
u8 demod_address;
/* request firmware for device */
int (*request_firmware)(struct dvb_frontend* fe, const struct firmware **fw, char* name);
};
#if IS_REACHABLE(CONFIG_DVB_BCM3510)
extern struct dvb_frontend* bcm3510_attach(const struct bcm3510_config* config,
struct i2c_adapter* i2c);
#else
static inline struct dvb_frontend* bcm3510_attach(const struct bcm3510_config* config,
struct i2c_adapter* i2c)
{
printk(KERN_WARNING "%s: driver disabled by Kconfig\n", __func__);
return NULL;
}
#endif // CONFIG_DVB_BCM3510
#endif
Annotation
- Immediate include surface: `linux/dvb/frontend.h`, `linux/firmware.h`.
- Detected declarations: `struct bcm3510_config`, `function bcm3510_attach`.
- 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.