drivers/iio/chemical/sps30.h

File Facts

System

Linux kernel

Corpus path

drivers/iio/chemical/sps30.h

Extension

.h

Size

1047 bytes

Lines

36

Domain

Driver Families

Bucket

drivers/iio

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h

Detected Declarations

• struct sps30_state
• struct sps30_ops
• struct sps30_state

Annotated Snippet

struct sps30_ops {
	int (*start_meas)(struct sps30_state *state);
	int (*stop_meas)(struct sps30_state *state);
	int (*read_meas)(struct sps30_state *state, __be32 *meas, size_t num);
	int (*reset)(struct sps30_state *state);
	int (*clean_fan)(struct sps30_state *state);
	int (*read_cleaning_period)(struct sps30_state *state, __be32 *period);
	int (*write_cleaning_period)(struct sps30_state *state, __be32 period);
	int (*show_info)(struct sps30_state *state);
};

struct sps30_state {
	/* serialize access to the device */
	struct mutex lock;
	struct device *dev;
	int state;
	/*
	 * priv pointer is solely for serdev driver private data. We keep it
	 * here because driver_data inside dev has been already used for iio and
	 * struct serdev_device doesn't have one.
	 */
	void *priv;
	const struct sps30_ops *ops;
};

int sps30_probe(struct device *dev, const char *name, void *priv, const struct sps30_ops *ops);

#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct sps30_state`, `struct sps30_ops`, `struct sps30_state`.
• Atlas domain: Driver Families / drivers/iio.
• 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.