include/linux/fsi-occ.h

File Facts

System

Linux kernel

Corpus path

include/linux/fsi-occ.h

Extension

.h

Size

715 bytes

Lines

28

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

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

Detected Declarations

• struct device

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0

#ifndef LINUX_FSI_OCC_H
#define LINUX_FSI_OCC_H

struct device;

#define OCC_RESP_CMD_IN_PRG		0xFF
#define OCC_RESP_SUCCESS		0
#define OCC_RESP_CMD_INVAL		0x11
#define OCC_RESP_CMD_LEN_INVAL		0x12
#define OCC_RESP_DATA_INVAL		0x13
#define OCC_RESP_CHKSUM_ERR		0x14
#define OCC_RESP_INT_ERR		0x15
#define OCC_RESP_BAD_STATE		0x16
#define OCC_RESP_CRIT_EXCEPT		0xE0
#define OCC_RESP_CRIT_INIT		0xE1
#define OCC_RESP_CRIT_WATCHDOG		0xE2
#define OCC_RESP_CRIT_OCB		0xE3
#define OCC_RESP_CRIT_HW		0xE4

#define OCC_MAX_RESP_WORDS		2048

int fsi_occ_submit(struct device *dev, const void *request, size_t req_len,
		   void *response, size_t *resp_len);

#endif /* LINUX_FSI_OCC_H */

Annotation

• Detected declarations: `struct device`.
• 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.