drivers/platform/wmi/tests/Kconfig

Source file repositories/reference/linux-study-clean/drivers/platform/wmi/tests/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/platform/wmi/tests/Kconfig
Extension: [no extension]
Size: 835 bytes
Lines: 28
Domain: Driver Families
Bucket: drivers/platform
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
#
# ACPI WMI KUnit tests
#

config ACPI_WMI_MARSHALLING_KUNIT_TEST
	tristate "KUnit Test for ACPI-WMI marshalling" if !KUNIT_ALL_TESTS
	depends on KUNIT
	default KUNIT_ALL_TESTS
	help
	  This builds unit tests for the ACPI-WMI marshalling code.

	  For more information on KUnit and unit tests in general, please refer
	  to the KUnit documentation in Documentation/dev-tools/kunit/.

	  If unsure, say N.

config ACPI_WMI_STRING_KUNIT_TEST
	tristate "KUnit Test for ACPI-WMI string conversion" if !KUNIT_ALL_TESTS
	depends on KUNIT
	default KUNIT_ALL_TESTS
	help
	  This builds unit tests for the ACPI-WMI string conversion code.
	  For more information on KUnit and unit tests in general, please refer
	  to the KUnit documentation in Documentation/dev-tools/kunit/.

	  If unsure, say N.

Annotation

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