drivers/net/ipa/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/net/ipa/Kconfig
Extension: [no extension]
Size: 838 bytes
Lines: 24
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

config QCOM_IPA
	tristate "Qualcomm IPA support"
	depends on NET && QCOM_SMEM
	depends on ARCH_QCOM || COMPILE_TEST
	depends on INTERCONNECT
	depends on QCOM_RPROC_COMMON || (QCOM_RPROC_COMMON=n && COMPILE_TEST)
	depends on QCOM_AOSS_QMP || QCOM_AOSS_QMP=n
	select QCOM_MDT_LOADER
	select QCOM_SCM
	select QCOM_QMI_HELPERS
	help
	  Choose Y or M here to include support for the Qualcomm
	  IP Accelerator (IPA), a hardware block present in some
	  Qualcomm SoCs.  The IPA is a programmable protocol processor
	  that is capable of generic hardware handling of IP packets,
	  including routing, filtering, and NAT.  Currently the IPA
	  driver supports only basic transport of network traffic
	  between the AP and modem.

	  Note that if selected, the selection type must match that
	  of QCOM_Q6V5_COMMON (Y or M).

	  If unsure, say N.

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.