arch/arm/mach-imx/ssi-fiq-ksym.c

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-imx/ssi-fiq-ksym.c

Extension

.c

Size

405 bytes

Lines

18

Domain

Architecture Layer

Bucket

arch/arm

Inferred role

Architecture Layer: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.

Dependency Surface

• linux/module.h
• linux/platform_data/asoc-imx-ssi.h

Detected Declarations

• export imx_ssi_fiq_tx_buffer
• export imx_ssi_fiq_rx_buffer
• export imx_ssi_fiq_start
• export imx_ssi_fiq_end
• export imx_ssi_fiq_base

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0-only
/*
 * Exported ksyms for the SSI FIQ handler
 *
 * Copyright (C) 2009, Sascha Hauer <s.hauer@pengutronix.de>
 */

#include <linux/module.h>

#include <linux/platform_data/asoc-imx-ssi.h>

EXPORT_SYMBOL(imx_ssi_fiq_tx_buffer);
EXPORT_SYMBOL(imx_ssi_fiq_rx_buffer);
EXPORT_SYMBOL(imx_ssi_fiq_start);
EXPORT_SYMBOL(imx_ssi_fiq_end);
EXPORT_SYMBOL(imx_ssi_fiq_base);

Annotation

• Immediate include surface: `linux/module.h`, `linux/platform_data/asoc-imx-ssi.h`.
• Detected declarations: `export imx_ssi_fiq_tx_buffer`, `export imx_ssi_fiq_rx_buffer`, `export imx_ssi_fiq_start`, `export imx_ssi_fiq_end`, `export imx_ssi_fiq_base`.
• Atlas domain: Architecture Layer / arch/arm.
• Implementation status: integration 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.