drivers/misc/amd-sbi/Kconfig

Source file repositories/reference/linux-study-clean/drivers/misc/amd-sbi/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/misc/amd-sbi/Kconfig
Extension: [no extension]
Size: 742 bytes
Lines: 23
Domain: Driver Families
Bucket: drivers/misc
Inferred role: Driver Families: build/configuration rule
Status: atlas-only

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.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0-only
config AMD_SBRMI_I2C
	tristate "AMD side band RMI support"
	depends on I3C_OR_I2C
	depends on ARM || ARM64 || COMPILE_TEST
	select REGMAP_I2C
	select REGMAP_I3C if I3C
	help
	  Side band RMI over I2C/I3C support for AMD out of band management.
	  This driver is intended to run on the BMC, not the managed node.

	  This driver can also be built as a module. If so, the module will
	  be called sbrmi-i2c.

config AMD_SBRMI_HWMON
	bool "SBRMI hardware monitoring"
	depends on AMD_SBRMI_I2C && HWMON
	depends on !(AMD_SBRMI_I2C=y && HWMON=m)
	help
	  This provides support for RMI device hardware monitoring. If enabled,
	  a hardware monitoring device will be created for each socket in
	  the system.

Annotation

Atlas domain: Driver Families / drivers/misc.
Implementation status: atlas-only.

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.