include/linux/iio/buffer.h
Source file repositories/reference/linux-study-clean/include/linux/iio/buffer.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/iio/buffer.h- Extension
.h- Size
- 2620 bytes
- Lines
- 83
- 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/sysfs.hlinux/iio/iio.h
Detected Declarations
struct iio_bufferenum iio_buffer_directionfunction iio_push_to_buffers_with_timestampfunction iio_push_to_buffers_with_ts
Annotated Snippet
#ifndef _IIO_BUFFER_GENERIC_H_
#define _IIO_BUFFER_GENERIC_H_
#include <linux/sysfs.h>
#include <linux/iio/iio.h>
struct iio_buffer;
enum iio_buffer_direction {
IIO_BUFFER_DIRECTION_IN,
IIO_BUFFER_DIRECTION_OUT,
};
int iio_push_to_buffers(struct iio_dev *indio_dev, const void *data);
int iio_pop_from_buffer(struct iio_buffer *buffer, void *data);
/**
* iio_push_to_buffers_with_timestamp() - push data and timestamp to buffers
* @indio_dev: iio_dev structure for device.
* @data: sample data
* @timestamp: timestamp for the sample data
*
* DEPRECATED: Use iio_push_to_buffers_with_ts() instead.
*
* Returns 0 on success, a negative error code otherwise.
*/
static inline int iio_push_to_buffers_with_timestamp(struct iio_dev *indio_dev,
void *data, int64_t timestamp)
{
if (ACCESS_PRIVATE(indio_dev, scan_timestamp)) {
size_t ts_offset = indio_dev->scan_bytes / sizeof(int64_t) - 1;
((int64_t *)data)[ts_offset] = timestamp;
}
return iio_push_to_buffers(indio_dev, data);
}
/**
* iio_push_to_buffers_with_ts() - push data and timestamp to buffers
* @indio_dev: iio_dev structure for device.
* @data: Pointer to sample data buffer.
* @data_total_len: The size of @data in bytes.
* @timestamp: Timestamp for the sample data.
*
* Pushes data to the IIO device's buffers. If timestamps are enabled for the
* device the function will store the supplied timestamp as the last element in
* the sample data buffer before pushing it to the device buffers. The sample
* data buffer needs to be large enough to hold the additional timestamp
* (usually the buffer should be at least indio->scan_bytes bytes large).
*
* Context: Any context.
* Return: 0 on success, a negative error code otherwise.
*/
static inline int iio_push_to_buffers_with_ts(struct iio_dev *indio_dev,
void *data, size_t data_total_len,
s64 timestamp)
{
if (unlikely(data_total_len < indio_dev->scan_bytes)) {
dev_err(&indio_dev->dev, "Undersized storage pushed to buffer\n");
return -ENOSPC;
}
return iio_push_to_buffers_with_timestamp(indio_dev, data, timestamp);
}
int iio_push_to_buffers_with_ts_unaligned(struct iio_dev *indio_dev,
const void *data, size_t data_sz,
int64_t timestamp);
bool iio_validate_scan_mask_onehot(struct iio_dev *indio_dev,
const unsigned long *mask);
int iio_device_attach_buffer(struct iio_dev *indio_dev,
struct iio_buffer *buffer);
#endif /* _IIO_BUFFER_GENERIC_H_ */
Annotation
- Immediate include surface: `linux/sysfs.h`, `linux/iio/iio.h`.
- Detected declarations: `struct iio_buffer`, `enum iio_buffer_direction`, `function iio_push_to_buffers_with_timestamp`, `function iio_push_to_buffers_with_ts`.
- 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.