drivers/net/ethernet/asix/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/net/ethernet/asix/Kconfig
Extension: [no extension]
Size: 888 bytes
Lines: 36
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

#
# Asix network device configuration
#

config NET_VENDOR_ASIX
	bool "Asix devices"
	default y
	help
	  If you have a network (Ethernet, non-USB, not NE2000 compatible)
	  interface based on a chip from ASIX, say Y.

if NET_VENDOR_ASIX

config SPI_AX88796C
	tristate "Asix AX88796C-SPI support"
	select PHYLIB
	depends on SPI
	depends on GPIOLIB
	help
	  Say Y here if you intend to use ASIX AX88796C attached in SPI mode.

config SPI_AX88796C_COMPRESSION
	bool "SPI transfer compression"
	default n
	depends on SPI_AX88796C
	help
	  Say Y here to enable SPI transfer compression. It saves up
	  to 24 dummy cycles during each transfer which may noticeably
	  speed up short transfers. This sets the default value that is
	  inherited by network interfaces during probe. It can be
	  changed at run time via spi-compression ethtool tunable.

	  If unsure say N.

endif # NET_VENDOR_ASIX

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.