drivers/misc/amd-sbi/rmi-core.h

File Facts

System

Linux kernel

Corpus path

drivers/misc/amd-sbi/rmi-core.h

Extension

.h

Size

1690 bytes

Lines

75

Domain

Driver Families

Bucket

drivers/misc

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/miscdevice.h
• linux/mutex.h
• linux/i2c.h
• linux/platform_device.h
• linux/regmap.h
• uapi/misc/amd-apml.h

Detected Declarations

• struct sbrmi_data
• enum sbrmi_reg
• enum sbrmi_msg_id
• function create_hwmon_sensor_device

Annotated Snippet

struct sbrmi_data {
	struct miscdevice sbrmi_misc_dev;
	struct regmap *regmap;
	/* Mutex locking */
	struct mutex lock;
	u32 pwr_limit_max;
	u8 dev_static_addr;
	u8 rev;
};

int rmi_mailbox_xfer(struct sbrmi_data *data, struct apml_mbox_msg *msg);
#ifdef CONFIG_AMD_SBRMI_HWMON
int create_hwmon_sensor_device(struct device *dev, struct sbrmi_data *data);
#else
static inline int create_hwmon_sensor_device(struct device *dev, struct sbrmi_data *data)
{
	return 0;
}
#endif
int create_misc_rmi_device(struct sbrmi_data *data, struct device *dev);
#endif /*_SBRMI_CORE_H_*/

Annotation

• Immediate include surface: `linux/miscdevice.h`, `linux/mutex.h`, `linux/i2c.h`, `linux/platform_device.h`, `linux/regmap.h`, `uapi/misc/amd-apml.h`.
• Detected declarations: `struct sbrmi_data`, `enum sbrmi_reg`, `enum sbrmi_msg_id`, `function create_hwmon_sensor_device`.
• Atlas domain: Driver Families / drivers/misc.
• 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.