drivers/net/ethernet/huawei/hinic3/Kconfig

Source file repositories/reference/linux-study-clean/drivers/net/ethernet/huawei/hinic3/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/net/ethernet/huawei/hinic3/Kconfig
Extension: [no extension]
Size: 629 bytes
Lines: 22
Domain: Driver Families
Bucket: drivers/net
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.
Touches IRQ or DMA behavior; this matters for the representative real-device path.

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
#
# Huawei driver configuration
#

config HINIC3
	tristate "Huawei 3rd generation network adapters (HINIC3) support"
	# Fields of HW and management structures are little endian and are
	# currently not converted
	depends on !CPU_BIG_ENDIAN
	depends on X86 || ARM64 || COMPILE_TEST
	depends on PCI_MSI && 64BIT
	select AUXILIARY_BUS
	select DIMLIB
	select PAGE_POOL
	help
	  This driver supports HiNIC 3rd gen Network Adapter (HINIC3).
	  The driver is supported on X86_64 and ARM64 little endian.

	  To compile this driver as a module, choose M here.
	  The module will be called hinic3.

Annotation

Atlas domain: Driver Families / drivers/net.
Implementation status: atlas-only.
IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.