drivers/bus/fsl-mc/Kconfig

Source file repositories/reference/linux-study-clean/drivers/bus/fsl-mc/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/bus/fsl-mc/Kconfig
Extension: [no extension]
Size: 762 bytes
Lines: 24
Domain: Driver Families
Bucket: drivers/bus
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
#
# DPAA2 fsl-mc bus
#
# Copyright (C) 2014-2016 Freescale Semiconductor, Inc.
#

config FSL_MC_BUS
	bool "QorIQ DPAA2 fsl-mc bus driver"
	depends on OF && (ARCH_LAYERSCAPE || (COMPILE_TEST && (ARM || ARM64 || X86_LOCAL_APIC || PPC)))
	select GENERIC_MSI_IRQ
	help
	  Driver to enable the bus infrastructure for the QorIQ DPAA2
	  architecture.  The fsl-mc bus driver handles discovery of
	  DPAA2 objects (which are represented as Linux devices) and
	  binding objects to drivers.

config FSL_MC_UAPI_SUPPORT
	bool "Management Complex (MC) userspace support"
	depends on FSL_MC_BUS
	help
	  Provides userspace support for interrogating, creating, destroying or
	  configuring DPAA2 objects exported by the Management Complex.

Annotation

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