include/linux/iio/timer/stm32-lptim-trigger.h

File Facts

System

Linux kernel

Corpus path

include/linux/iio/timer/stm32-lptim-trigger.h

Extension

.h

Size

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

Dependency Surface

• linux/iio/iio.h
• linux/iio/trigger.h

Detected Declarations

• function is_stm32_lptim_trigger

Annotated Snippet

#ifndef _STM32_LPTIM_TRIGGER_H_
#define _STM32_LPTIM_TRIGGER_H_

#include <linux/iio/iio.h>
#include <linux/iio/trigger.h>

#define LPTIM1_OUT	"lptim1_out"
#define LPTIM2_OUT	"lptim2_out"
#define LPTIM3_OUT	"lptim3_out"
#define LPTIM4_OUT	"lptim4_out"
#define LPTIM5_OUT	"lptim5_out"

#define LPTIM1_CH1	"lptim1_ch1"
#define LPTIM1_CH2	"lptim1_ch2"
#define LPTIM2_CH1	"lptim2_ch1"
#define LPTIM2_CH2	"lptim2_ch2"
#define LPTIM3_CH1	"lptim3_ch1"
#define LPTIM4_CH1	"lptim4_ch1"

#if IS_REACHABLE(CONFIG_IIO_STM32_LPTIMER_TRIGGER)
bool is_stm32_lptim_trigger(struct iio_trigger *trig);
#else
static inline bool is_stm32_lptim_trigger(struct iio_trigger *trig)
{
#if IS_ENABLED(CONFIG_IIO_STM32_LPTIMER_TRIGGER)
	pr_warn_once("stm32 lptim_trigger not linked in\n");
#endif
	return false;
}
#endif
#endif

Annotation

• Immediate include surface: `linux/iio/iio.h`, `linux/iio/trigger.h`.
• Detected declarations: `function is_stm32_lptim_trigger`.
• 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.