include/linux/soc/qcom/qcom-pbs.h

File Facts

System

Linux kernel

Corpus path

include/linux/soc/qcom/qcom-pbs.h

Extension

.h

Size

640 bytes

Lines

31

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

• linux/errno.h
• linux/types.h

Detected Declarations

• struct device_node
• struct pbs_dev
• function qcom_pbs_trigger_event

Annotated Snippet

#ifndef _QCOM_PBS_H
#define _QCOM_PBS_H

#include <linux/errno.h>
#include <linux/types.h>

struct device_node;
struct pbs_dev;

#if IS_ENABLED(CONFIG_QCOM_PBS)
int qcom_pbs_trigger_event(struct pbs_dev *pbs, u8 bitmap);
struct pbs_dev *get_pbs_client_device(struct device *client_dev);
#else
static inline int qcom_pbs_trigger_event(struct pbs_dev *pbs, u8 bitmap)
{
	return -ENODEV;
}

static inline struct pbs_dev *get_pbs_client_device(struct device *client_dev)
{
	return ERR_PTR(-ENODEV);
}
#endif

#endif

Annotation

• Immediate include surface: `linux/errno.h`, `linux/types.h`.
• Detected declarations: `struct device_node`, `struct pbs_dev`, `function qcom_pbs_trigger_event`.
• 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.