drivers/net/wwan/iosm/iosm_ipc_port.h
Source file repositories/reference/linux-study-clean/drivers/net/wwan/iosm/iosm_ipc_port.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/wwan/iosm/iosm_ipc_port.h- Extension
.h- Size
- 1245 bytes
- Lines
- 51
- Domain
- Driver Families
- Bucket
- drivers/net
- 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/wwan.hiosm_ipc_imem_ops.h
Detected Declarations
struct iosm_cdev
Annotated Snippet
struct iosm_cdev {
struct wwan_port *iosm_port;
struct iosm_imem *ipc_imem;
struct device *dev;
struct iosm_pcie *pcie;
enum wwan_port_type port_type;
struct ipc_mem_channel *channel;
enum ipc_channel_id chl_id;
};
/**
* ipc_port_init - Allocate IPC port & register to wwan subsystem for AT/MBIM
* communication.
* @ipc_imem: Pointer to iosm_imem structure
* @ipc_port_cfg: IPC Port Config
*
* Returns: 0 on success & NULL on failure
*/
struct iosm_cdev *ipc_port_init(struct iosm_imem *ipc_imem,
struct ipc_chnl_cfg ipc_port_cfg);
/**
* ipc_port_deinit - Free IPC port & unregister port with wwan subsystem.
* @ipc_port: Array of pointer to the ipc port data-struct
*/
void ipc_port_deinit(struct iosm_cdev *ipc_port[]);
#endif
Annotation
- Immediate include surface: `linux/wwan.h`, `iosm_ipc_imem_ops.h`.
- Detected declarations: `struct iosm_cdev`.
- Atlas domain: Driver Families / drivers/net.
- 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.