include/linux/iio/afe/rescale.h

File Facts

System

Linux kernel

Corpus path

include/linux/iio/afe/rescale.h

Extension

.h

Size

833 bytes

Lines

37

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/types.h
• linux/iio/iio.h

Detected Declarations

• struct device
• struct rescale
• struct rescale_cfg
• struct rescale

Annotated Snippet

struct rescale_cfg {
	enum iio_chan_type type;
	int (*props)(struct device *dev, struct rescale *rescale);
};

struct rescale {
	const struct rescale_cfg *cfg;
	struct iio_channel *source;
	struct iio_chan_spec chan;
	struct iio_chan_spec_ext_info *ext_info;
	bool chan_processed;
	s32 numerator;
	s32 denominator;
	s32 offset;
};

int rescale_process_scale(struct rescale *rescale, int scale_type,
			  int *val, int *val2);
int rescale_process_offset(struct rescale *rescale, int scale_type,
			   int scale, int scale2, int schan_off,
			   int *val, int *val2);
#endif /* __IIO_RESCALE_H__ */

Annotation

• Immediate include surface: `linux/types.h`, `linux/iio/iio.h`.
• Detected declarations: `struct device`, `struct rescale`, `struct rescale_cfg`, `struct rescale`.
• 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.