drivers/hid/amd-sfh-hid/Kconfig

Source file repositories/reference/linux-study-clean/drivers/hid/amd-sfh-hid/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/hid/amd-sfh-hid/Kconfig
Extension: [no extension]
Size: 570 bytes
Lines: 19
Domain: Driver Families
Bucket: drivers/hid
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-or-later
menu "AMD SFH HID Support"
	depends on X86_64 || COMPILE_TEST
	depends on PCI

config AMD_SFH_HID
	tristate "AMD Sensor Fusion Hub"
	depends on X86
	help
	  If you say yes to this option, support will be included for the
	  AMD Sensor Fusion Hub.
	  This driver will enable sensors functionality on AMD platforms
	  starting from 17h family of RYZEN parts.

	  This driver can also be built as a module. If so, the module will
	  be called amd-sfh.
	  Say Y or M here if you want to support AMD SFH. If unsure, say N.
endmenu

Annotation

Atlas domain: Driver Families / drivers/hid.
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.