drivers/net/ethernet/intel/libie/Kconfig

Source file repositories/reference/linux-study-clean/drivers/net/ethernet/intel/libie/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/net/ethernet/intel/libie/Kconfig
Extension: [no extension]
Size: 743 bytes
Lines: 26
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.

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
# Copyright (C) 2024 Intel Corporation

config LIBIE
	tristate
	select LIBETH
	help
	  libie (Intel Ethernet library) is a common library built on top of
	  libeth and containing vendor-specific routines shared between several
	  Intel Ethernet drivers.

config LIBIE_ADMINQ
	tristate
	help
	  Helper functions used by Intel Ethernet drivers for administration
	  queue command interface (aka adminq).

config LIBIE_FWLOG
	tristate
	select LIBIE_ADMINQ
	help
	  Library to support firmware logging on device that have support
	  for it. Firmware logging is using admin queue interface to communicate
	  with the device. Debugfs is a user interface used to config logging
	  and dump all collected logs.

Annotation

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