drivers/net/ethernet/freescale/fman/fman.c

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/freescale/fman/fman.c

Extension

.c

Size

83442 bytes

Lines

2914

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/fsl/guts.h
• linux/platform_device.h
• linux/slab.h
• linux/delay.h
• linux/module.h
• linux/of_platform.h
• linux/clk.h
• linux/of_address.h
• linux/of_irq.h
• linux/interrupt.h
• linux/libfdt_env.h
• fman.h
• fman_muram.h
• fman_keygen.h

Detected Declarations

• struct fman_iram_regs
• struct fman_fpm_regs
• struct fman_bmi_regs
• struct fman_qmi_regs
• struct fman_dma_regs
• struct fman_hwp_regs
• struct fman_state_struct
• struct fman_cfg
• enum fman_dma_aid_mode
• function fman_exceptions
• function fman_bus_error
• function call_mac_isr
• function hw_port_id_to_sw_port_id
• function set_port_order_restoration
• function set_port_liodn
• function enable_rams_ecc
• function disable_rams_ecc
• function fman_defconfig
• function dma_init
• function fpm_init
• function bmi_init
• function qmi_init
• function hwp_init
• function enable
• function set_exception
• function resume
• function fill_soc_specific_params
• function is_init_done
• function free_init_resources
• function bmi_err_event
• function qmi_err_event
• function dma_err_event
• function fpm_err_event
• function muram_err_intr
• function qmi_event
• function enable_time_stamp
• function clear_iram
• function get_exception_flag
• function get_module_event
• function set_size_of_fifo
• function set_num_of_tasks
• function set_num_of_open_dmas
• function fman_config
• function fman_reset
• function fman_init
• function fman_set_exception
• function fman_register_intr
• function fman_unregister_intr

Annotated Snippet

module_init(fman_load);

static void __exit fman_unload(void)
{
	platform_driver_unregister(&fman_driver);
}
module_exit(fman_unload);

MODULE_LICENSE("Dual BSD/GPL");
MODULE_DESCRIPTION("Freescale DPAA Frame Manager driver");

Annotation

• Immediate include surface: `linux/fsl/guts.h`, `linux/platform_device.h`, `linux/slab.h`, `linux/delay.h`, `linux/module.h`, `linux/of_platform.h`, `linux/clk.h`, `linux/of_address.h`.
• Detected declarations: `struct fman_iram_regs`, `struct fman_fpm_regs`, `struct fman_bmi_regs`, `struct fman_qmi_regs`, `struct fman_dma_regs`, `struct fman_hwp_regs`, `struct fman_state_struct`, `struct fman_cfg`, `enum fman_dma_aid_mode`, `function fman_exceptions`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• 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.