drivers/hwmon/sch56xx-common.h

File Facts

System

Linux kernel

Corpus path

drivers/hwmon/sch56xx-common.h

Extension

.h

Size

1127 bytes

Lines

25

Domain

Driver Families

Bucket

drivers/hwmon

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/mutex.h
• linux/regmap.h

Detected Declarations

• struct sch56xx_watchdog_data

Annotated Snippet

#include <linux/mutex.h>
#include <linux/regmap.h>

struct sch56xx_watchdog_data;

struct regmap *devm_regmap_init_sch56xx(struct device *dev, struct mutex *lock, u16 addr,
					const struct regmap_config *config);
int sch56xx_regmap_read16(struct regmap *map, unsigned int reg, unsigned int *val);
int sch56xx_regmap_write16(struct regmap *map, unsigned int reg, unsigned int val);

int sch56xx_read_virtual_reg(u16 addr, u16 reg);
int sch56xx_write_virtual_reg(u16 addr, u16 reg, u8 val);
int sch56xx_read_virtual_reg16(u16 addr, u16 reg);
int sch56xx_read_virtual_reg12(u16 addr, u16 msb_reg, u16 lsn_reg,
			       int high_nibble);

void sch56xx_watchdog_register(struct device *parent, u16 addr, u32 revision,
			       struct mutex *io_lock, int check_enabled);

Annotation

• Immediate include surface: `linux/mutex.h`, `linux/regmap.h`.
• Detected declarations: `struct sch56xx_watchdog_data`.
• Atlas domain: Driver Families / drivers/hwmon.
• 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.