include/pcmcia/ds.h
Source file repositories/reference/linux-study-clean/include/pcmcia/ds.h
File Facts
- System
- Linux kernel
- Corpus path
include/pcmcia/ds.h- Extension
.h- Size
- 7689 bytes
- Lines
- 275
- Domain
- Repository Root And Misc
- Bucket
- include
- Inferred role
- Repository Root And Misc: operation-table or driver-model contract
- Status
- pattern implementation candidate
Why This File Exists
Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
- Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
- Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
- Touches IRQ or DMA behavior; this matters for the representative real-device path.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/mod_devicetable.hpcmcia/device_id.hlinux/device.hlinux/interrupt.hpcmcia/ss.hlinux/atomic.h
Detected Declarations
struct pcmcia_socketstruct pcmcia_devicestruct config_tstruct net_devicestruct pcmcia_dynidsstruct pcmcia_driverstruct pcmcia_device
Annotated Snippet
struct device_driver drv;
struct pcmcia_dynids dynids;
};
/* driver registration */
int pcmcia_register_driver(struct pcmcia_driver *driver);
void pcmcia_unregister_driver(struct pcmcia_driver *driver);
/**
* module_pcmcia_driver() - Helper macro for registering a pcmcia driver
* @__pcmcia_driver: pcmcia_driver struct
*
* Helper macro for pcmcia drivers which do not do anything special in module
* init/exit. This eliminates a lot of boilerplate. Each module may only use
* this macro once, and calling it replaces module_init() and module_exit().
*/
#define module_pcmcia_driver(__pcmcia_driver) \
module_driver(__pcmcia_driver, pcmcia_register_driver, \
pcmcia_unregister_driver)
/* for struct resource * array embedded in struct pcmcia_device */
enum {
PCMCIA_IOPORT_0,
PCMCIA_IOPORT_1,
PCMCIA_IOMEM_0,
PCMCIA_IOMEM_1,
PCMCIA_IOMEM_2,
PCMCIA_IOMEM_3,
PCMCIA_NUM_RESOURCES,
};
struct pcmcia_device {
/* the socket and the device_no [for multifunction devices]
uniquely define a pcmcia_device */
struct pcmcia_socket *socket;
char *devname;
u8 device_no;
/* the hardware "function" device; certain subdevices can
* share one hardware "function" device. */
u8 func;
struct config_t *function_config;
struct list_head socket_device_list;
/* device setup */
unsigned int irq;
struct resource *resource[PCMCIA_NUM_RESOURCES];
resource_size_t card_addr; /* for the 1st IOMEM resource */
unsigned int vpp;
unsigned int config_flags; /* CONF_ENABLE_ flags below */
unsigned int config_base;
unsigned int config_index;
unsigned int config_regs; /* PRESENT_ flags below */
unsigned int io_lines; /* number of I/O lines */
/* Is the device suspended? */
u16 suspended:1;
/* Flags whether io, irq, win configurations were
* requested, and whether the configuration is "locked" */
u16 _irq:1;
u16 _io:1;
u16 _win:4;
u16 _locked:1;
/* Flag whether a "fuzzy" func_id based match is
* allowed. */
u16 allow_func_id_match:1;
/* information about this device */
u16 has_manf_id:1;
u16 has_card_id:1;
u16 has_func_id:1;
u16 reserved:4;
u8 func_id;
u16 manf_id;
u16 card_id;
char *prod_id[4];
u64 dma_mask;
struct device dev;
/* data private to drivers */
Annotation
- Immediate include surface: `linux/mod_devicetable.h`, `pcmcia/device_id.h`, `linux/device.h`, `linux/interrupt.h`, `pcmcia/ss.h`, `linux/atomic.h`.
- Detected declarations: `struct pcmcia_socket`, `struct pcmcia_device`, `struct config_t`, `struct net_device`, `struct pcmcia_dynids`, `struct pcmcia_driver`, `struct pcmcia_device`.
- Atlas domain: Repository Root And Misc / include.
- Implementation status: pattern implementation candidate.
- IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.
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.