include/linux/firmware/xlnx-zynqmp-ufs.h

File Facts

System

Linux kernel

Corpus path

include/linux/firmware/xlnx-zynqmp-ufs.h

Extension

.h

Size

840 bytes

Lines

39

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• function zynqmp_pm_is_mphy_tx_rx_config_ready
• function zynqmp_pm_is_sram_init_done
• function zynqmp_pm_set_sram_bypass
• function zynqmp_pm_get_ufs_calibration_values

Annotated Snippet

#ifndef __FIRMWARE_XLNX_ZYNQMP_UFS_H__
#define __FIRMWARE_XLNX_ZYNQMP_UFS_H__

#if IS_REACHABLE(CONFIG_ZYNQMP_FIRMWARE)
int zynqmp_pm_is_mphy_tx_rx_config_ready(bool *is_ready);
int zynqmp_pm_is_sram_init_done(bool *is_done);
int zynqmp_pm_set_sram_bypass(void);
int zynqmp_pm_get_ufs_calibration_values(u32 *val);
#else
static inline int zynqmp_pm_is_mphy_tx_rx_config_ready(bool *is_ready)
{
	return -ENODEV;
}

static inline int zynqmp_pm_is_sram_init_done(bool *is_done)
{
	return -ENODEV;
}

static inline int zynqmp_pm_set_sram_bypass(void)
{
	return -ENODEV;
}

static inline int zynqmp_pm_get_ufs_calibration_values(u32 *val)
{
	return -ENODEV;
}
#endif

#endif /* __FIRMWARE_XLNX_ZYNQMP_UFS_H__ */

Annotation

• Detected declarations: `function zynqmp_pm_is_mphy_tx_rx_config_ready`, `function zynqmp_pm_is_sram_init_done`, `function zynqmp_pm_set_sram_bypass`, `function zynqmp_pm_get_ufs_calibration_values`.
• Atlas domain: Core OS / Core Kernel Interface.
• 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.